summaryrefslogtreecommitdiff
path: root/Documentation
diff options
context:
space:
mode:
authorLibravatar Junio C Hamano <gitster@pobox.com>2013-03-27 10:58:07 -0700
committerLibravatar Junio C Hamano <gitster@pobox.com>2013-03-27 10:58:07 -0700
commit8617715cc09b7422fe31189f9476f6ade73ede70 (patch)
tree7c62d215a31c9e990753b2bc1e8aee1870f06c4c /Documentation
parentMerge branch 'master' of git://git.bogomips.org/git-svn (diff)
parentMore fixes for 1.8.2.1 (diff)
downloadtgif-8617715cc09b7422fe31189f9476f6ade73ede70.tar.xz
Merge branch 'maint'
* maint: More fixes for 1.8.2.1 merge-tree: fix typo in merge-tree.c::unresolved git-commit doc: describe use of multiple `-m` options git-pull doc: fix grammo ("conflicts" is plural)
Diffstat (limited to 'Documentation')
-rw-r--r--Documentation/RelNotes/1.8.2.1.txt3
-rw-r--r--Documentation/git-commit.txt2
-rw-r--r--Documentation/git-pull.txt2
3 files changed, 6 insertions, 1 deletions
diff --git a/Documentation/RelNotes/1.8.2.1.txt b/Documentation/RelNotes/1.8.2.1.txt
index 23977562a9..b4cf3cccde 100644
--- a/Documentation/RelNotes/1.8.2.1.txt
+++ b/Documentation/RelNotes/1.8.2.1.txt
@@ -66,3 +66,6 @@ Fixes since v1.8.2
to file scope static, but a few functions in graph.c were used by
CGit from sideways bypassing the entry points of the API the
in-tree users use.
+
+ * "git merge-tree" had a typo in the logic to detect d/f conflicts,
+ which caused it to segfault in some cases.
diff --git a/Documentation/git-commit.txt b/Documentation/git-commit.txt
index 24a99ccc99..05f8297368 100644
--- a/Documentation/git-commit.txt
+++ b/Documentation/git-commit.txt
@@ -137,6 +137,8 @@ OPTIONS
-m <msg>::
--message=<msg>::
Use the given <msg> as the commit message.
+ If multiple `-m` options are given, their values are
+ concatenated as separate paragraphs.
-t <file>::
--template=<file>::
diff --git a/Documentation/git-pull.txt b/Documentation/git-pull.txt
index c975743230..24ab07a3f8 100644
--- a/Documentation/git-pull.txt
+++ b/Documentation/git-pull.txt
@@ -218,7 +218,7 @@ $ git merge origin/next
------------------------------------------------
-If you tried a pull which resulted in a complex conflicts and
+If you tried a pull which resulted in complex conflicts and
would want to start over, you can recover with 'git reset'.