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

2014-02-18 Thread John Keeping
On Tue, Feb 18, 2014 at 07:56:20AM +0100, Guido Günther wrote: 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

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

2014-02-18 Thread Jonathan Nieder
Hi, Guido Günther wrote: Without this when maintaining stable branches it's easy to forget to use -x to track where a patch was cherry-picked from. [...] --- a/Documentation/git-cherry-pick.txt +++ b/Documentation/git-cherry-pick.txt @@ -215,6 +215,14 @@ the working tree. spending extra

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

2014-02-18 Thread brian m. carlson
On Tue, Feb 18, 2014 at 09:49:13AM -0800, Jonathan Nieder wrote: Can you say more about the context? Why is it important to record the original commit id? Is it a matter of keeping a reminder of the commits' similarity (which cherry-pick without '-x' does ok by reusing the same message) or

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

2014-02-17 Thread Guido Günther
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