From: Junio C Hamano <gitster@pobox.com>
To: "Jan Krüger" <jk@jk.gs>
Cc: git@vger.kernel.org, gitster@pobox.com
Subject: Re: [PATCH] Documentation: clarify information about 'ident' attribute
Date: Thu, 30 Oct 2008 12:30:23 -0700 [thread overview]
Message-ID: <7vfxmdev8w.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20081030191433.710aff11@perceptron> (Jan Krüger's message of "Thu, 30 Oct 2008 19:14:33 +0100")
"Jan Krüger" <jk@jk.gs> writes:
> The documentation spoke of the attribute being set "to" a path; this can
> mistakenly be interpreted as "the attribute needs to have its value set to
> some kind of path". This clarifies things (and also calls the object ID a
> hash rather than a name because that might be confusing too).
I'd agree with the first change, but not with the second. "object name"
has been the official name of these hexadecimal thingy for a long time
(see the glossary).
prev parent reply other threads:[~2008-10-30 19:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-30 18:14 [PATCH] Documentation: clarify information about 'ident' attribute Jan Krüger
2008-10-30 19:30 ` Junio C Hamano [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=7vfxmdev8w.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jk@jk.gs \
/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).