| commit | 5034fdea3017304fa37e50b3bd40c392503ebfd2 | |
| author | Felipe Contreras <felipe.contreras@gmail.com> | |
| Thu, 11 Apr 2013 00:07:11 +0000 (10 19:07 -0500) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Thu, 11 Apr 2013 16:04:39 +0000 (11 09:04 -0700) | ||
| tree | 725f4871b7dc9314e5d74ee4896e1f78b54fc171 | treesnapshot (tar.gz zip) |
| parent | c096955c5bb8e20186cc7c07d4d12b77ddcd01c6 | commitdiff |
transport-helper: improve push messages
If there's already a remote-helper tracking ref, we can fetch the SHA-1
to report proper push messages (as opposed to always reporting
[new branch]).
The remote-helper currently can specify the old SHA-1 to avoid this
problem, but there's no point in forcing all remote-helpers to be aware
of git commit ids; they should be able to be agnostic of them.
Signed-off-by: Felipe Contreras <felipe.contreras@gmail.com>
Reviewed-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
If there's already a remote-helper tracking ref, we can fetch the SHA-1
to report proper push messages (as opposed to always reporting
[new branch]).
The remote-helper currently can specify the old SHA-1 to avoid this
problem, but there's no point in forcing all remote-helpers to be aware
of git commit ids; they should be able to be agnostic of them.
Signed-off-by: Felipe Contreras <felipe.contreras@gmail.com>
Reviewed-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| t/t5801-remote-helpers.sh | diffblobblamehistory | |
| transport-helper.c | diffblobblamehistory |