All of
 help / color / mirror / Atom feed
From: Linus Torvalds <>
To: Matthias Urlichs <>
Subject: Re: The coolest merge EVER!
Date: Fri, 24 Jun 2005 12:22:28 -0700 (PDT)	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Fri, 24 Jun 2005, Matthias Urlichs wrote:

> 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.

No no. 

A merge is a one-way thing. I merged Paul's tree, but Paul didn't merge 
mine. His is still independent, and you can still pull his tree without 
getting the rest of git, and Paul can still continue to work on his tree 
as if I never merged it at all.

Now, merging back isn't as easy: if any gitk changes get done in my 
"union" tree, Paul can't just pull those, becasue they now end up being 
linked to the history of the unified thing, so when pulling, he'd now end 
up getting all of the regular git stuff too.

Which is probably acceptable, but Junio's point was that this is not a 
symmetric setup: git is like a black hole that never lets any information 
escape, and once you've been sucked into a git archive, you end up not 
being able to separate it.

Or rather, you _can_ separate out pieces of it, but now it's a matter of
cherry-picking, not automatic merges. Of course, people want to be able to 
do that anyway, and normally that will also merge back perfectly, so 
there's no huge downside, except that we should make it fairly easy.


      parent reply	other threads:[~2005-06-24 19:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-22 21:46 The coolest merge EVER! Linus Torvalds
2005-06-23  0:12 ` Jon Seymour
2005-06-23  0:24   ` Jeff Garzik
2005-06-24  0:44 ` Junio C Hamano
2005-06-24 11:54   ` Matthias Urlichs
2005-06-24 17:49     ` Daniel Barkalow
2005-06-24 19:22     ` Linus Torvalds [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.