From: "Shawn O. Pearce" <spearce@spearce.org>
To: Bill Lear <rael@zopyra.com>
Cc: Jakub Narebski <jnareb@gmail.com>, git@vger.kernel.org
Subject: Re: Why is git clone not checking out files?
Date: Tue, 30 Jan 2007 13:22:37 -0500 [thread overview]
Message-ID: <20070130182237.GC26415@spearce.org> (raw)
In-Reply-To: <17855.35845.922009.364704@lisa.zopyra.com>
Bill Lear <rael@zopyra.com> wrote:
> Ok, well, I certainly did not issue git clone --bare, it was just a
> plain ol' clone:
>
> % git clone /repos/git/project
>
> and no checkout ensued. Can I fix this somehow? I've tried the clone
> several times with no success. Is there anything I can check in the
> source repo (the above /repos/git/project) to see why it would not be
> working?
I've seen this happen if HEAD in the source repository does not point
at a branch, or points at a commit which doesn't exist. Though I
usually also see an error about how HEAD isn't a valid object name...
--
Shawn.
next prev parent reply other threads:[~2007-01-30 18:22 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 [this message]
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
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=20070130182237.GC26415@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=rael@zopyra.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).