Andreas Krey wrote:
> On Tue, 21 Mar 2017 13:33:35 +, Jeff King wrote:
>> Probably "format-patch | sed | am -3" is your best bet if you want to
>> modify the patches in transit _and_ have the user just use normal git
>> tools.
>
> Except that 'git am' doesn't have --no-commit like cherry-pick
On Tue, 21 Mar 2017 13:33:35 +, Jeff King wrote:
...
> Probably "format-patch | sed | am -3" is your best bet if you want to
> modify the patches in transit _and_ have the user just use normal git
> tools.
Except that 'git am' doesn't have --no-commit like cherry-pick does. :-(
It's always
On Tue, Mar 21, 2017 at 06:07:34PM +0100, Andreas Krey wrote:
> > There's "cherry-pick --edit".
>
> Yes, but. I'm in a toolchain, not a user. I'm a command that let
> the user cherry-pick specific things, and I need to edit out the things
> that made the original commit eligible to be picked in
On Tue, 21 Mar 2017 13:00:05 +, Jeff King wrote:
...
> > I have an slightly unusual usecase for cherry-pick:
> > I want to modify the commit message that is used in the process,
> > e.g. do an d/^PROP:/ on it, but unfortunately -m does something
> > else here.
> >
...
>
> There's
On Tue, Mar 21, 2017 at 05:05:20PM +0100, Andreas Krey wrote:
> Hi all,
>
> I have an slightly unusual usecase for cherry-pick:
> I want to modify the commit message that is used in the process,
> e.g. do an d/^PROP:/ on it, but unfortunately -m does something
> else here.
>
> And there is no
Hi all,
I have an slightly unusual usecase for cherry-pick:
I want to modify the commit message that is used in the process,
e.g. do an d/^PROP:/ on it, but unfortunately -m does something
else here.
And there is no --message here for good reason, as cherry-pick
can pick multiple commits and so
6 matches
Mail list logo
