Re: [RFC] cherry-pick using multiple parents to implement -x

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

 



Shawn O. Pearce wrote:
>"Stephen R. van den Berg" <srb@xxxxxxx> wrote:
>> Whereas cherry-pick would (optionally) generate a cousin reference for every
>> commit it picks.

>Sorry for wandering into a thread in the middle.  But we've already
>been down this road before, and decided the additional header wasn't
>worth it from cherry-pick.  What's changed?

I'm not familiar with the old thread.  Any pointers?  (I tried googling,
but couldn't seem to find it).

>  The fact that gitk
>wants to hyperlink this?  Why can't it just regex out a string of
>hex digits longer than 6 and see if there is a commit that matches?

To avoid (accidental) duplication of the old thread, I'll try and read
that first.
-- 
Sincerely,
           Stephen R. van den Berg.
The Horkheimer Effect: "The odds of it being cloudy are directly proportional
to the importance of an astronomical event."
--
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]

  Powered by Linux