Re: Why is git clone not checking out files?

From: Bill Lear <rael@zopyra.com>
Date: Jan 30, 2007, 19:11 UTC
Message-ID: <17855.39008.920685.62837@lisa.zopyra.com>
In-Reply-To: <Pine.LNX.4.64.0701301058250.3611@woody.linux-foundation.org>

On Tuesday, January 30, 2007 at 11:04:57 (-0800) Linus Torvalds writes:

Show 6 quoted lines

>...
>Of course, I do agree that it'sa fairly confusing way to set up a repo, 
>and you generally shouldn't do it, but Bill did it that way explicitly. 
>Maybe he didn't do it "on purpose", but git at no point in time had any 
>way to know that Bill wanted somethign else. Nothing he did was "wrong", 
>and it's quite possible that it's what he could have meant to do.

My setup was prompted by advice I got here. Perhaps I misunderstood. I thought the way to set up a shared public repo for my collaborators was to git --bare init-db --shared, then do a git fetch from the upstream repo. I want to be able to push into my public repo from one or more of my private repos, hence the need (I was told) for he bare option.

>Anyway, it's certainly easy to fix. Bill, you can either:
>
> - just rename the "topic" branch to "master"

I don't think I want this. I want to know I'm on the topic branch of that repo, anything else really makes me nervous.

> - change the HEAD to point to "topic" rather than "master".

Same for this...[Thanks for the advice, nevertheless.]

I wonder if the original repo I pulled from is just messed up. Ahh -- I see Shawn just replied saying I needed to fetch in a different way. I shall peruse that and report clarity of vision when achieved...

Bill