[PATCH] revert.c: Allow to specify -x via git-config

Without this when maintaining stable branches it's easy to forget to use -x to track where a patch was cherry-picked from. Signed-off-by: Guido Günther a...@sigxcpu.org --- Documentation/git-cherry-pick.txt | 8 builtin/revert.c | 10 ++ 2 files changed, 18

[PATCH v2 0/3] Allow to configure cherry-pick's record origin

* add --record-origin for symmetry with config file option and --no-record-origin * Add docs to git-config as well Guido Günther (3): revert.c: Allow to specify -x via git-config revert.c: Add --record-origin revert.c Allow to override cherrypick.recordOrigin Documentation/config.txt

[PATCH v2 2/3] revert.c: Add --record-origin

This makes sure we have a command line option that corresponds with the config file option. --- Documentation/git-cherry-pick.txt | 1 + builtin/revert.c | 2 +- 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/Documentation/git-cherry-pick.txt

[PATCH v2 1/3] revert.c: Allow to specify -x via git-config

Without this when maintaining stable branches it's easy to forget to use -x to track where a patch was cherry-picked from. --- Documentation/config.txt | 4 Documentation/git-cherry-pick.txt | 8 builtin/revert.c | 14 +- 3 files changed, 25

[PATCH v2 3/3] revert.c Allow to override cherrypick.recordOrigin

--no-record-origin can be used by scripts to be sure to not record origin information when cherry-picking. --- Documentation/git-cherry-pick.txt | 4 builtin/revert.c | 6 ++ 2 files changed, 10 insertions(+) diff --git a/Documentation/git-cherry-pick.txt