| commit | b056620f6fe7f05834716109fa79e7880a11bc36 | |
| author | Felipe Contreras <felipe.contreras@gmail.com> | |
| Fri, 3 May 2013 23:41:59 +0000 (3 18:41 -0500) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Sun, 5 May 2013 18:10:53 +0000 (5 11:10 -0700) | ||
| tree | 10f1889cd18adc142843e6725fafbf982f8b7b92 | treesnapshot (tar.gz zip) |
| parent | 571cdfd4e0a4cc24e215a5d5f0cb24292a9d7929 | 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 |