From: Junio C Hamano <gitster@pobox.com>
To: Thomas Ackermann <th.acker@arcor.de>
Cc: davvid@gmail.com, git@vger.kernel.org
Subject: Re: [PATCH v3 2/6] Change 'git' to 'Git' whenever the whole system is referred to #1
Date: Tue, 22 Jan 2013 18:32:39 -0800 [thread overview]
Message-ID: <7vr4lck4s8.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <7vfw1slpig.fsf@alter.siamese.dyndns.org> (Junio C. Hamano's message of "Tue, 22 Jan 2013 16:19:35 -0800")
In Documentation/git-rev-parse.txt, there is this bit:
--resolve-git-dir <path>::
Check if <path> is a valid git-dir or a git-file pointing to
a valid git-dir. If <path> is a valid git-dir the resolved path to
git-dir will be printed.
I think the author invented the word "git-dir" to mean what we
ordinarily call $GIT_DIR (i.e. the directory that contains the
repository data), and used "git-file" to mean what the code and
error messages call "gitfile". I think it is better to leave these
in lowercase, but we would need them in the glossary, probably after
rewriting the latter to "gitfile". The former may want to be
rewritten to "gitdir" or even "$GIT_DIR".
next prev parent reply other threads:[~2013-01-23 2:33 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-20 20:16 Aw: Re: [PATCH 1/2] Change old system name 'GIT' to 'Git' Thomas Ackermann
2013-01-20 21:08 ` Junio C Hamano
2013-01-21 18:36 ` [PATCH v2 0/6] GIT, Git, git Thomas Ackermann
2013-01-21 19:56 ` Junio C Hamano
2013-01-21 20:01 ` Junio C Hamano
2013-01-21 18:38 ` [PATCH v2 1/6] Change old system name 'GIT' to 'Git' Thomas Ackermann
2013-01-21 18:40 ` [PATCH v2 2/6] Change 'git' to 'Git' whenever the whole system is referred to #1 Thomas Ackermann
2013-01-21 18:51 ` Aw: [PATCH v2 0/6] GIT, Git, git Thomas Ackermann
2013-01-21 19:12 ` [PATCH v3 " Thomas Ackermann
2013-01-21 19:16 ` [PATCH v3 1/6] Change old system name 'GIT' to 'Git' Thomas Ackermann
2013-01-22 0:39 ` Junio C Hamano
2013-01-22 9:44 ` Aw: " Thomas Ackermann
2013-01-22 16:45 ` Junio C Hamano
2013-01-21 19:17 ` [PATCH v3 2/6] Change 'git' to 'Git' whenever the whole system is referred to #1 Thomas Ackermann
2013-01-22 0:41 ` Junio C Hamano
2013-01-22 23:48 ` Junio C Hamano
2013-01-23 0:19 ` Junio C Hamano
2013-01-23 2:24 ` Junio C Hamano
2013-01-23 2:32 ` Junio C Hamano [this message]
2013-01-21 19:19 ` [PATCH v3 3/6] Change 'git' to 'Git' whenever the whole system is referred to #2 Thomas Ackermann
2013-01-23 0:53 ` Junio C Hamano
2013-01-23 2:48 ` Junio C Hamano
2013-01-23 3:44 ` David Aguilar
2013-01-23 4:17 ` Junio C Hamano
2013-01-23 8:58 ` Aw: " Thomas Ackermann
2013-02-01 0:46 ` Junio C Hamano
2013-02-01 18:04 ` Aw: " Thomas Ackermann
2013-02-01 18:37 ` Junio C Hamano
2013-02-01 18:06 ` [PATCH 1/6] fixup! fixup! " Thomas Ackermann
2013-02-01 18:07 ` [PATCH 2/6] fixup! fixup! fixup! Change 'git' to 'Git' whenever the whole system is referred to #1 Thomas Ackermann
2013-02-01 19:43 ` Jonathan Nieder
2013-02-01 20:16 ` Junio C Hamano
2013-02-01 18:08 ` [PATCH 3/6] fixup! Documentation: avoid poor-man's small caps Thomas Ackermann
2013-02-01 18:44 ` Junio C Hamano
2013-02-01 18:10 ` [PATCH 4/6] Fix places where 'Git' should be 'git Thomas Ackermann
2013-02-01 18:11 ` [PATCH 5/6] Add a description for 'gitfile' to glossary Thomas Ackermann
2013-02-01 18:41 ` Junio C Hamano
2013-02-01 19:26 ` Junio C Hamano
2013-02-01 19:46 ` Jonathan Nieder
2013-02-01 18:12 ` [PATCH 6/6] Use consistent links for User Manual and Everyday Git; Fix a quoting error Thomas Ackermann
2013-02-01 18:43 ` Junio C Hamano
2013-02-01 19:51 ` Jonathan Nieder
2013-02-01 20:17 ` Junio C Hamano
2013-02-01 20:25 ` Aw: " Thomas Ackermann
2013-01-21 19:21 ` [PATCH v3 4/6] Change 'git' to 'Git' whenever the whole system is referred to #3 Thomas Ackermann
2013-01-23 2:49 ` Junio C Hamano
2013-01-21 19:22 ` [PATCH v3 5/6] Change 'git' to 'Git' whenever the whole system is referred to #4 Thomas Ackermann
2013-01-23 3:16 ` Junio C Hamano
2013-01-21 19:24 ` [PATCH v3 6/6] Add rule for when to use 'git' and when to use 'Git' Thomas Ackermann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7vr4lck4s8.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=davvid@gmail.com \
--cc=git@vger.kernel.org \
--cc=th.acker@arcor.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).