git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: How to get a directory filled with v2.6.11?

From
Linus Torvalds <torvalds@osdl.org>
Date
Jul 13, 2005, 20:46 UTC
Message-ID
<Pine.LNX.4.58.0507131342190.17536@g5.osdl.org>
In-Reply-To
<7vvf3ewig0.fsf@assigned-by-dhcp.cox.net>
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.

			Linus
Previous: Junio C Hamano
Message 5 of 5 in “How to get a directory filled with v2.6.11?”
  1. Marc SingerJul 12, 2005
  2. Matthias UrlichsJul 12, 2005
  3. Linus TorvaldsJul 13, 2005
  4. Junio C HamanoJul 13, 2005
  5. Linus TorvaldsJul 13, 2005

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.