Minor typo; see below. On 07/11/2011 11:14 AM, Bert Wesarg wrote: > The documentation for logging updates in git-update-ref, doesn't make it > clear that only a specific subset of refs are honored by this variable. > > Signed-off-by: Bert Wesarg <bert.wesarg@xxxxxxxxxxxxxx> > > --- > > The initial justification in 4057deb (Junio C Hamano, 2006-10-08), leaves > the impression, that a blacklist would have made more sense, than the > current whitelist. Maybe we can change this? > --- > Documentation/config.txt | 4 +++- > Documentation/git-update-ref.txt | 5 +++-- > 2 files changed, 6 insertions(+), 3 deletions(-) > > diff --git a/Documentation/config.txt b/Documentation/config.txt > index c631d1c..dd44122 100644 > --- a/Documentation/config.txt > +++ b/Documentation/config.txt > @@ -344,7 +344,9 @@ core.logAllRefUpdates:: > SHA1, the date/time and the reason of the update, but > only when the file exists. If this configuration > variable is set to true, missing "$GIT_DIR/logs/<ref>" > - file is automatically created for branch heads. > + file is automatically created for branch heads (i.e. under > + refs/heads/), remote reafs (i.e. under refs/remotes/), s/reafs/refs/ -- Michael Haggerty mhagger@xxxxxxxxxxxx http://softwareswirl.blogspot.com/ -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html