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

Re: The coolest merge EVER!

From
Daniel Barkalow <barkalow@iabervon.org>
Date
Jun 24, 2005, 17:49 UTC
Message-ID
<Pine.LNX.4.21.0506241332150.30848-100000@iabervon.org>
In-Reply-To
<pan.2005.06.24.11.54.51.598627@smurf.noris.de>
On Fri, 24 Jun 2005, Matthias Urlichs wrote:
Show 8 quoted lines
> Hi, Junio C Hamano wrote:
> 
> > I suspect there
> > would be a massive additional support needed if you want to make it easy
> > for Paul to pull changes made to gitk in your tree.
> 
> I don't think that's possible; after all, the trees are now merged, so any
> pull would fetch all of Linus' tree.
Linus could do:
 git-read-tree gitk-head
 git-update-cache gitk
 git-commit-tree `write-tree` -p gitk-head > gitk-patched-head
 git-read-tree HEAD
 git merge gitk-patched-head
(or, better, use a separate index file for the gitk index)
(to commit changes to the gitk script made in a git working directory)

The change I proposed earlier would be so that the system would know what was going on and users wouldn't have to. Then someone who didn't know that gitk was (also) a separate project and just committed changes to it would still generate gitk commits when appropriate.

	-Daniel
*This .sig left intentionally blank*
Previous: Matthias UrlichsNext: Linus Torvalds
Message 6 of 7 in “The coolest merge EVER!”
  1. Linus TorvaldsJun 22, 2005
  2. Jon SeymourJun 23, 2005
  3. Jeff GarzikJun 23, 2005
  4. Junio C HamanoJun 24, 2005
  5. Matthias UrlichsJun 24, 2005
  6. Daniel BarkalowJun 24, 2005
  7. Linus TorvaldsJun 24, 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.