aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2009-06-20 23:48:46 -0700
committerJunio C Hamano <gitster@pobox.com>2009-06-20 23:48:46 -0700
commit3ba4f3a9fc68ba4c5a0064107e8993c5fc5b684f (patch)
treeae4db4348f007b3603534d720690869bc5c4b3e0
parentef52aafa0f8b1d34f2ecd9b58f2198711c87cab3 (diff)
parentcd12f536129357d5347c1953db69bde68b5f46c9 (diff)
downloadgit-3ba4f3a9fc68ba4c5a0064107e8993c5fc5b684f.tar.gz
git-3ba4f3a9fc68ba4c5a0064107e8993c5fc5b684f.tar.xz
Merge branch 'maint-1.6.2' into maint
* maint-1.6.2: git-show-ref.txt: remove word and make consistent git-svn documentation: fix typo in 'rebase vs. pull/merge' section use xstrdup, not strdup in ll-merge.c
-rw-r--r--Documentation/git-show-ref.txt4
-rw-r--r--Documentation/git-svn.txt2
-rw-r--r--ll-merge.c8
3 files changed, 7 insertions, 7 deletions
diff --git a/Documentation/git-show-ref.txt b/Documentation/git-show-ref.txt
index 2f173fff3..98e294aa8 100644
--- a/Documentation/git-show-ref.txt
+++ b/Documentation/git-show-ref.txt
@@ -24,7 +24,7 @@ The --exclude-existing form is a filter that does the inverse, it shows the
refs from stdin that don't exist in the local repository.
Use of this utility is encouraged in favor of directly accessing files under
-in the `.git` directory.
+the `.git` directory.
OPTIONS
-------
@@ -50,7 +50,7 @@ OPTIONS
-s::
--hash::
- Only show the SHA1 hash, not the reference name. When also using
+ Only show the SHA1 hash, not the reference name. When combined with
--dereference the dereferenced tag will still be shown after the SHA1.
--verify::
diff --git a/Documentation/git-svn.txt b/Documentation/git-svn.txt
index 1c4089466..74be8435c 100644
--- a/Documentation/git-svn.txt
+++ b/Documentation/git-svn.txt
@@ -615,7 +615,7 @@ pulled or merged from. This is because the author favored
If you use `git svn set-tree A..B` to commit several diffs and you do
not have the latest remotes/git-svn merged into my-branch, you should
use `git svn rebase` to update your work branch instead of `git pull` or
-`git merge`. `pull`/`merge' can cause non-linear history to be flattened
+`git merge`. `pull`/`merge` can cause non-linear history to be flattened
when committing into SVN, which can lead to merge commits reversing
previous commits in SVN.
diff --git a/ll-merge.c b/ll-merge.c
index 81c02ad05..f7c2bc927 100644
--- a/ll-merge.c
+++ b/ll-merge.c
@@ -238,7 +238,7 @@ static int read_merge_config(const char *var, const char *value, void *cb)
if (!strcmp(var, "merge.default")) {
if (value)
- default_ll_merge = strdup(value);
+ default_ll_merge = xstrdup(value);
return 0;
}
@@ -272,7 +272,7 @@ static int read_merge_config(const char *var, const char *value, void *cb)
if (!strcmp("name", ep)) {
if (!value)
return error("%s: lacks value", var);
- fn->description = strdup(value);
+ fn->description = xstrdup(value);
return 0;
}
@@ -295,14 +295,14 @@ static int read_merge_config(const char *var, const char *value, void *cb)
* file named by %A, and signal that it has done with zero exit
* status.
*/
- fn->cmdline = strdup(value);
+ fn->cmdline = xstrdup(value);
return 0;
}
if (!strcmp("recursive", ep)) {
if (!value)
return error("%s: lacks value", var);
- fn->recursive = strdup(value);
+ fn->recursive = xstrdup(value);
return 0;
}