Re: [ANNOUNCE] GIT 1.5.4

From
Junichi Uekawa <hidden>
Date
2016-06-15 22:44:09
Reply to
Junichi Uekawa, 2016-06-15
Hi,


When I was idly googling around for traces of VCS and popularity,
noticed that Git is actually pretty popular.  Googling for 'gitweb'
and 'viewcvs' and other comparative web-frontend variants floating in
the cyberspace I get these number of hits (in rough estimate) :

10000000 CVS
1000000 SVN
100000 Git
10000 Mercurial / Darcs
1000 Bzr

This is crude, and I'm sure someone else will come up with a better
estimate. The point is, when there are so many users, people don't
read the lists or the changelog, but rely on manuals, and be surprised
with this change.

quoted
   - Using dashed forms of git commands (e.g. "git-commit") from the
     command line has been informally deprecated since early 2006, but
     now it officially is, and will be removed in the future.  Use
     dash-less forms (e.g. "git commit") instead.
I was wondering why I use the git-xxx format so much (in muscle, and
in scripts). And realized I have the following reasons:

1. That's the form documented in the manual pages (generated from asciidoc)

2. That's the name manual pages are in.

3. Linus said it's better (3 years ago), and I thought so too.
   (Situation has changed, bash has better completion for 'git'
   commands, so that's no longer valid)

4. There was a GNU Interactive Tools with the same name 'git', so it
was better to avoid confusion then. (This is still the case with
Debian, where the sysadmin can choose whether to make 'git' (GNU
Interactive Tools) the default, or our beloved git.

5. There are many documentations floating around.

6. I'm used to it.


regards,
	junichi
-- 
dancer@{debian.org,netfort.gr.jp}   Debian Project
Thread (23 messages) 23 messages, 13 authors, last reply 2016-06-15
Keyboard shortcuts
hback out one level
jnext message in thread / next series-diff position
kprevious message in thread / previous series-diff position
ldrill in
Escclose help / fold thread tree
?toggle this help