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

Re: "True" git merge in git-pasky

From
FRFrancois Romieu <romieu@fr.zoreil.com>
Date
Apr 19, 2005, 23:40 UTC
Message-ID
<20050419234057.GA14807@electric-eye.fr.zoreil.com>
In-Reply-To
<20050419035107.GB5554@pasky.ji.cz>

Petr Baudis <pasky@ucw.cz> : [...]

Show 11 quoted lines
> Now you decided to do a little bit of parallel development and stick
> your patches not ready for 2.6.12 to a separate tree. That's fine, do
> 
> 	git fork experimental ~/linux-2.6.experimental
> 
> and get some coffee. (It takes about 8 minutes here, but I think git
> isn't at fault - it is probably all spent in
> 
> 	read-tree $(tree-id)
> 	checkout-cache -a
> 	update-cache --refresh
Tip of the day: cat the whole tree to /dev/null before the fork

-- Ueimor

Previous: Petr BaudisNext: Junio C Hamano
Message 4 of 10 in “"True" git merge in git-pasky”
  1. Petr BaudisApr 19, 2005
  2. bert hubertApr 19, 2005
  3. Petr BaudisApr 19, 2005
  4. Francois RomieuApr 19, 2005
  5. [RFC] Possible strategy cleanup for git add/remove/diff etc.Junio C Hamano, Apr 20, 2005
  6. Linus TorvaldsApr 20, 2005
  7. Junio C HamanoApr 20, 2005
  8. Linus TorvaldsApr 20, 2005
  9. Junio C HamanoApr 20, 2005
  10. Junio C HamanoApr 21, 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.