From: Daniel Hulme <st@istic.org>
To: git@vger.kernel.org
Subject: Re: Can't figure out some sense from the git-commit-tree man page
Date: Fri, 17 Aug 2007 17:55:19 +0100 [thread overview]
Message-ID: <20070817165519.GA28614@istic.org> (raw)
In-Reply-To: <20070817163034.GA11151@glandium.org>
[-- Attachment #1: Type: text/plain, Size: 1737 bytes --]
On Fri, Aug 17, 2007 at 06:30:34PM +0200, Mike Hommey wrote:
> Hi,
>
> The git-commit-tree man page reads:
> A commit encapsulates:
>
> · all parent object ids
>
> · author name, email and date
>
> · committer name and email and the commit time.
> If not provided, "git-commit-tree" uses your name, hostname and domain to
> provide author and committer info. This can be overridden by either
> .git/config file, or using the following environment variables.
> (...)
>
> The "If not provided" part doesn't make sense. If you're not setting the
> author and committer in your config or environment, how are you supposed
> to provide it ?
Makes sense to me. I interpreted it as:
If not provided (by one of the ways I'm about to mention), the default
is ... This default can be overridden by ...
I can understand how it might be read differently, though. Assuming my
reading is correct, might something along these lines be clearer:
To find author and committer info, "git-commit-tree" first looks at
these environment variables:
...
If they are not set, it tries the keys user.name and user.email from
the .git/config file. Finally, it falls back to using your name,
hostname, and domain.
Even clearer, though this might be a bit extreme, would be to not
mention .git/config and say it reads the global or repository-specific
keys using git-config.
--
"I like talking to Rabbit. He talks about sensible things. He doesn't
use long, difficult words, like Owl. He uses short, easy words, like
'What about lunch?' and 'Help yourself, Pooh.' I suppose, really, I
ought to go and see Rabbit." A. A. Milne, 'The House at Pooh Corner'
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2007-08-17 17:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-17 16:30 Can't figure out some sense from the git-commit-tree man page Mike Hommey
2007-08-17 16:52 ` Johannes Schindelin
2007-08-17 16:56 ` Mike Hommey
2007-08-17 17:09 ` Johannes Schindelin
2007-08-17 17:16 ` Jakub Narebski
2007-08-17 17:04 ` J. Bruce Fields
2007-08-17 17:23 ` Mike Hommey
2007-08-17 17:36 ` J. Bruce Fields
2007-08-17 20:13 ` [PATCH] Clarify commit-tree documentation Mike Hommey
2007-08-17 23:51 ` Junio C Hamano
2007-08-17 16:55 ` Daniel Hulme [this message]
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=20070817165519.GA28614@istic.org \
--to=st@istic.org \
--cc=git@vger.kernel.org \
/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).