From: Michael Haggerty <mhagger@alum.mit.edu>
Date: Tue, 12 Jul 2011 04:39:20 GMT
Subject: Re: [PATCH] Documentation: clearly specify what refs are honored by core.logAllRefUpdates
Message-ID: <4E1BCFF8.9030000@alum.mit.edu>
In-Reply-To: <c63583df97ff8dd596d16d4471041d6ebedb67e8.1310375571.git.bert.wesarg@googlemail.com>

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@googlemail.com>
> 
> ---
> 
> 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@alum.mit.edu
http://softwareswirl.blogspot.com/