summaryrefslogtreecommitdiff
path: root/Documentation/git-send-pack.txt
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2008-12-04 02:00:12 (GMT)
committerJunio C Hamano <gitster@pobox.com>2008-12-10 05:42:44 (GMT)
commit1b5b465fbde9515e04bd1e8524a208c92af3555e (patch)
treed00c3e751d8ddee85e01d034f912419eb49afb3f /Documentation/git-send-pack.txt
parent9e8eceab73e9f6a1e9349b1c14d4db0c035ac1ba (diff)
downloadgit-1b5b465fbde9515e04bd1e8524a208c92af3555e.zip
git-1b5b465fbde9515e04bd1e8524a208c92af3555e.tar.gz
git-1b5b465fbde9515e04bd1e8524a208c92af3555e.tar.bz2
Document "git-reset --merge"
The commit log message for the feature made it sound as if this is a saner version of --mixed, but the use case presented makes it clear that it is a better variant of --hard when your changes and somebody else's changes are mixed together. Perhaps we would want to rewrite the example that shows the use of --hard not to talk about recovering from a failed merge? Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'Documentation/git-send-pack.txt')
0 files changed, 0 insertions, 0 deletions