Re: [RFC/PATCH 2/2] Teach commit to handle CHERRY_HEAD automatically

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Feb 15, 2011 at 6:47 PM, Jonathan Nieder <jrnieder@xxxxxxxxx> wrote:
> I meant the following sequence of operations:
>
> Â Â Â Â# by the way, does this set CHERRY_PICK_HEAD?
> Â Â Â Âgit cherry-pick --no-commit F
> Â Â Â Âgit commit -C F-prime

CHERRY_PICK_HEAD is not written if you use --no-commit.  I'm going to
punt here and say that's not my itch, thus...

> But that was a silly example --- -C takes care of authorship on its
> own. ÂA better example might be
>
> Â Â Â Âgit cherry-pick --no-commit F
> Â Â Â Âgit commit -F the-message
>
> or
>
> Â Â Â Âgit cherry-pick --no-commit F
> Â Â Â Âgit commit --amend -C F-prime


Because CHERRY_PICK_HEAD wasn't written, commit in this case behaves
as it did before this series.

j.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]