Linus Torvalds <[EMAIL PROTECTED]> writes:
> On Mon, 11 Jul 2005, Eric W. Biederman wrote:
>> I guess I was expecting to pull from one tree into another unrelated
>> tree. Getting a tree with two heads and then be able to merge them
> You can do it, but you have to do it by hand. It's a valid operation, but
> it's not an operation I want people to do by mistake, so it's not
> something the trivial helper scripts help with.
> The way to do it by hand is to just use something stupid that doesn't
> understand what it's doing anyway, and just copy the files over. "cp -a"
> or "rsync" works fine. Then just do "git resolve" by hand. It's not very
> hard at all, but it's definitely something that should be a special case.
Ok. Only the dumb methods are allowed.
>> A couple of questions.
>> 1) Does git-clone-script when packed copy the entire repository
>> or just take a couple of slices of the tree where you have
> It only gets the objects needed for the references, nothing more.
> So if you only get one branch, it will leave the objects that are specific
> to other branches alone.
Hmm. As I recall reading the code it grabs everything that is
in .git/refs/*. So I would actually expect it to grab all of the
branches. My real question was different. With a clone it
appears to just get the objects used to compose a tree object,
but none of the history available by looking at the commit
parents is obtained. Not at all what I would expect for
an operation named clone.
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