| commit | d931455acf1cf1a21a4f10fd99fc2bd9bbefa7a9 | |
| author | Ævar Arnfjörð Bjarmason <avarab@gmail.com> | |
| Fri, 31 Aug 2018 20:10:00 +0000 (31 20:10 +0000) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Fri, 31 Aug 2018 21:04:06 +0000 (31 14:04 -0700) | ||
| tree | 2a32321bedf73d1f45555ab5279ba8a76433544c | treesnapshot (tar.gz zip) |
| parent | 6b0b0677f6d92932bacd73981a47724b543dfd90 | commitdiff |
push doc: remove confusing mention of remote merger
Saying that "git push <remote> <src>:<dst>" won't push a merger of
<src> and <dst> to <dst> is clear from the rest of the context here,
so mentioning it is redundant, furthermore the mention of "EXAMPLES
below" isn't specific or useful.
This phrase was originally added in 149f6ddfb3 ("Docs: Expand
explanation of the use of + in git push refspecs.", 2009-02-19), as
can be seen in that change the point of the example being cited was to
show that force pushing can leave unreferenced commits on the
remote. It's enough that we explain that in its own section, it
doesn't need to be mentioned here.
Signed-off-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Saying that "git push <remote> <src>:<dst>" won't push a merger of
<src> and <dst> to <dst> is clear from the rest of the context here,
so mentioning it is redundant, furthermore the mention of "EXAMPLES
below" isn't specific or useful.
This phrase was originally added in 149f6ddfb3 ("Docs: Expand
explanation of the use of + in git push refspecs.", 2009-02-19), as
can be seen in that change the point of the example being cited was to
show that force pushing can leave unreferenced commits on the
remote. It's enough that we explain that in its own section, it
doesn't need to be mentioned here.
Signed-off-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| Documentation/git-push.txt | diffblobblamehistory |