Re: [PATCH] add post-fetch hook
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Dec 26, 2011, 08:09 UTC
- Message-ID
- <7vhb0n92jx.fsf@alter.siamese.dyndns.org>
- In-Reply-To
- <m3liq0fwkz.fsf@localhost.localdomain>
Jakub Narebski <jnareb@gmail.com> writes:
> One thing that needs to be specified is what should happen if the hook > changes "the refname at the remote" part...
Hmm, good eyes.
The mechanism is to allow the hook to rewrite what happened during the fetch. If we decided refs/heads/master on the remote that points at the commit $X should update refs/remotes/origin/master, we tell that to the hook, and the hook reads it. The hook may tell us to pretend that we fetched refs/heads/next on the remote that points at the commit $Y should update refs/remotes/origin/pu. In FETCH_HEAD we leave where the commit was fetched from and hook will affect that information (which is used in the resulting merge commit log message), but otherwise I do not think anything unexpected would happen, as tracking refs do not record where the stuff came from (perhaps they are in reflog? I didn't check).