Documentation Source Text

Check-in [36bacb0ca7]
Login

Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.

Overview
Comment:Fix a typo in the whynotgit.html page.
Downloads: Tarball | ZIP archive
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA3-256: 36bacb0ca74ae42a50c485184e6468fb295a822361a365095b2062f08a806557
User & Date: drh 2018-04-11 03:33:53.824
Context
2018-04-11
11:29
Fix duplicate ticket link in the change log for 3.23.1. (check-in: 4d52786c5d user: drh tags: trunk)
03:33
Fix a typo in the whynotgit.html page. (check-in: 36bacb0ca7 user: drh tags: trunk)
2018-04-10
18:53
Fix another typo in whynotgit.html (check-in: dc2c4c372b user: drh tags: trunk)
Changes
Unified Diff Ignore Whitespace Patch
Changes to pages/whynotgit.in.
︙︙
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43

check-in.  But Git makes it very difficult to move in the other
direction.  Given some historical check-in, it is quite challenging
in Git to find out what came next.  It can be done, but it is sufficiently
difficult and slow that nobody ever does it.  There is no button in
GitHub that shows the descendents of a check-in.

<p>
This is a deal-breaker, a show-stopper.  The principle maintainer
of SQLite cannot function effectively without being able to view
the successors of a check-in.  This one issue is sufficient reason
to not use Git, in the view of the designer of SQLite.

<li><p>
The mental model for Git is needlessly complex and consequently
distracts attention from software under development.  A user of Git








|








29
30
31
32
33
34
35
36
37
38
39
40
41
42
43

check-in.  But Git makes it very difficult to move in the other
direction.  Given some historical check-in, it is quite challenging
in Git to find out what came next.  It can be done, but it is sufficiently
difficult and slow that nobody ever does it.  There is no button in
GitHub that shows the descendents of a check-in.

<p>
This is a deal-breaker, a show-stopper.  The principal maintainer
of SQLite cannot function effectively without being able to view
the successors of a check-in.  This one issue is sufficient reason
to not use Git, in the view of the designer of SQLite.

<li><p>
The mental model for Git is needlessly complex and consequently
distracts attention from software under development.  A user of Git
︙︙