[Cc: git@xxxxxxxxxxxxxxx]
Horst H. von Brand wrote:
> @@ -30,12 +30,12 @@ and executable, it is called with three parameters:
>
> $GIT_DIR/hooks/update refname sha1-old sha1-new
>
> -The refname parameter is relative to $GIT_DIR; e.g. for the
> -master head this is "refs/heads/master". Two sha1 are the
> -object names for the refname before and after the update. Note
> -that the hook is called before the refname is updated, so either
> -sha1-old is 0{40} (meaning there is no such ref yet), or it
> -should match what is recorded in refname.
> +The refname parameter is relative to $GIT_DIR; e.g. for the master
> +head this is "refs/heads/master". The two sha1 are the object names
^^^^
> +for the refname before and after the update. Note that the hook is
> +called before the refname is updated, so either sha1-old is 0{40}
> +(meaning there is no such ref yet), or it should match what is
> +recorded in refname.
First, it does some reformatting instead of making documentation
always use SHA-1. Second, it does not replace sha1 by SHA-1 (sic!).
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
-
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