Re: [RFC] cherry-pick using multiple parents to implement -x
- From
Paolo Bonzini <bonzini@gnu.org>
- Date
- Sep 8, 2008, 13:04 UTC
- Message-ID
- <48C522F6.7090308@gnu.org>
- In-Reply-To
- <20080908115129.GA19031@cuci.nl>
Show 8 quoted lines
> commit 7df437e56b5a2c5ec7140dd097b517563db4972c > tree a006f20b481d811ccb4846534ef6394be5bc78a8 > parent ff1e8bfcd69e5e0ee1a3167e80ef75b611f72123 > parent bbb896d8e10f736bfda8f587c0009c358c9a8599 > cousin 6ffaecc7d8b2c3c188a2efa5977a6e6605d878d9 > cousin a1184d85e8752658f02746982822f43f32316803 > author Junio C Hamano <gitster@pobox.com> 1220153499 -0700 > committer Junio C Hamano <gitster@pobox.com> 1220153499 -0700
What about "origin", and making it propagated through cherry-picks? In other words, if I "cherry-pick -x" A generating B, and do the same on B generating C, C should have A as origin. Also, "git cherry-pick -n -x" should add the commit to a list of origins somewhere so that "git commit" can reuse it.
Furthermore, "git cherry" should use origins if available.
Paolo