On Wed, 13 Jul 2005, Junio C Hamano wrote:
> I do not think git-cherry would be that useful in this context.
> Nobody upstream is merging things into your development trail,
> started at the private commit you made based on the 2.6.11 tree.
No, the point being that he (or anybody else) could move the commits as
patches, one by one, from his 2.6.11 base to whatever later base that _is_
in the commit history.
It's really the same issue as with cherry-picking: you do commits one at a
time as diffs, see if that diff already exists in the destination stream,
and if not, you try to apply it as a patch and re-commit it with the old
commit message in a new place in history.
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html