From: Thomas Rast <trast@student.ethz.ch>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: <git@vger.kernel.org>, Johan Herland <johan@herland.net>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: [PATCH 1/4] Documentation/notes: describe effect of environment and configuration
Date: Tue, 4 May 2010 11:24:26 +0200 [thread overview]
Message-ID: <201005041124.26533.trast@student.ethz.ch> (raw)
In-Reply-To: <20100503234140.GA27483@progeny.tock>
Jonathan Nieder wrote:
> +core.notesRef::
> + By default, 'git notes' and other commands read and manipulate
> + the notes referred to by `refs/notes/commits`. This
> + configuration item allows one to specify an alternative
> + default ref (to be overridden by environment variables or
> + command-line options).
> +
> +notes.displayRef::
> + Which refs, in addition to the default set by `core.notesRef`
> + or 'GIT_NOTES_REF', for 'git log' to read notes from when
> + showing commit messages. Can be a (fully qualified) ref name
> + or glob. You may also specify this configuration variable
> + several times.
> ++
> +This setting can be overridden with the 'GIT_NOTES_DISPLAY_REF'
> +environment variable.
I noticed you copied the rest of the description, but not these,
verbatim. If the intention was to separate the specification of the
notes format exposed in git-config(1),
[...] This ref is expected to contain files named after the full
SHA-1 of the commit they annotate. The ref must be fully
qualified.
If such a file exists in the given ref, the referenced blob is
read, and appended to the commit message, separated by a "Notes
(<refname>):" line (shortened to "Notes:" in the case of
"refs/notes/commits"). If the given ref itself does not exist, it
is not an error, but means that no notes should be printed.
from the description of the option. I agree to the idea, but maybe we
should also do the same in git-config(1). For example, it could be
added to the NOTES section of git-notes(1) that already describes some
implementation details.
You also describe the warning semantics only for
GIT_NOTES_DISPLAY_REF, not for notes.displayRef. I see the config
options as the main feature, and the variable as a mere convenience
(but others may disagree) so I would put the full semantics into the
config descriptions.
Otherwise, ack.
--
Thomas Rast
trast@{inf,student}.ethz.ch
next prev parent reply other threads:[~2010-05-04 9:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-03 23:36 [PATCH 0/4] Documentation/notes: fill out the man page a little Jonathan Nieder
2010-05-03 23:41 ` [PATCH 1/4] Documentation/notes: describe effect of environment and configuration Jonathan Nieder
2010-05-04 9:24 ` Thomas Rast [this message]
2010-05-03 23:42 ` [PATCH 2/4] Documentation/notes: adjust description to use configuration section Jonathan Nieder
2010-05-03 23:42 ` [PATCH 3/4] Documentation/notes: describe content of notes Jonathan Nieder
2010-05-04 9:28 ` Thomas Rast
2010-05-04 9:55 ` Johan Herland
2010-05-05 3:23 ` Jeff King
2010-05-03 23:47 ` [PATCH 4/4] Documentation/notes: nitpicks Jonathan Nieder
2010-05-04 7:09 ` Thomas Rast
2010-05-04 7:23 ` Jonathan Nieder
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=201005041124.26533.trast@student.ethz.ch \
--to=trast@student.ethz.ch \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=johan@herland.net \
--cc=jrnieder@gmail.com \
/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).