diff options
author | Junio C Hamano <gitster@pobox.com> | 2015-03-25 21:58:45 -0700 |
---|---|---|
committer | Junio C Hamano <gitster@pobox.com> | 2015-04-29 13:28:10 -0700 |
commit | d45366e8aa922037e7e84c3f35924d2b1399a453 (patch) | |
tree | be02e30d9f0719dcbbc227bcf55dfee32bf3de25 /Documentation/git-annotate.txt | |
parent | merge: handle FETCH_HEAD internally (diff) | |
download | tgif-d45366e8aa922037e7e84c3f35924d2b1399a453.tar.xz |
merge: deprecate 'git merge <message> HEAD <commit>' syntax
We had this in "git merge" manual for eternity:
'git merge' <msg> HEAD <commit>...
[This] syntax (<msg> `HEAD` <commit>...) is supported for
historical reasons. Do not use it from the command line or in
new scripts. It is the same as `git merge -m <msg> <commit>...`.
With the update to "git merge" to make it understand what is
recorded in FETCH_HEAD directly, including Octopus merge cases, we
now can rewrite the use of this syntax in "git pull" with a simple
"git merge FETCH_HEAD".
Also there are quite a few fallouts in the test scripts, and it
turns out that "git cvsimport" also uses this old syntax to record
a merge.
Judging from this result, I would not be surprised if dropping the
support of the old syntax broke scripts people have written and been
relying on for the past ten years. But at least we can start the
deprecation process by throwing a warning message when the syntax is
used.
With luck, we might be able to drop the support in a few years.
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'Documentation/git-annotate.txt')
0 files changed, 0 insertions, 0 deletions