From: Bill Lear <rael@zopyra.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Jakub Narebski <jnareb@gmail.com>,
"Shawn O. Pearce" <spearce@spearce.org>,
git@vger.kernel.org
Subject: Re: Why is git clone not checking out files?
Date: Tue, 30 Jan 2007 13:11:28 -0600 [thread overview]
Message-ID: <17855.39008.920685.62837@lisa.zopyra.com> (raw)
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:
>...
>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
next prev parent reply other threads:[~2007-01-30 19:11 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-30 18:05 Why is git clone not checking out files? Bill Lear
2007-01-30 18:15 ` Jakub Narebski
2007-01-30 18:18 ` Bill Lear
2007-01-30 18:22 ` Shawn O. Pearce
2007-01-30 18:29 ` Bill Lear
2007-01-30 18:41 ` Linus Torvalds
2007-01-30 18:49 ` Jakub Narebski
2007-01-30 19:04 ` Linus Torvalds
2007-01-30 19:11 ` Bill Lear [this message]
2007-01-30 19:15 ` Johannes Schindelin
2007-01-30 19:36 ` Bill Lear
2007-01-30 19:43 ` Bill Lear
2007-01-30 19:54 ` Bill Lear
2007-01-30 20:38 ` Bill Lear
2007-01-30 19:18 ` Jakub Narebski
2007-01-31 9:56 ` Jakub Narebski
2007-01-30 19:03 ` Bill Lear
2007-01-30 19:09 ` Shawn O. Pearce
2007-01-30 19:17 ` Jakub Narebski
2007-01-30 19:27 ` Bill Lear
2007-01-30 19:33 ` Linus Torvalds
2007-01-30 20:00 ` Linus Torvalds
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=17855.39008.920685.62837@lisa.zopyra.com \
--to=rael@zopyra.com \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=spearce@spearce.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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.