From: "Jakub Narebski" <jnareb@gmail.com>
To: git@vger.kernel.org
Cc: "Bill Lear" <rael@zopyra.com>,
"Shawn O. Pearce" <spearce@spearce.org>,
"Linus Torvalds" <torvalds@linux-foundation.org>
Subject: Re: Why is git clone not checking out files?
Date: Wed, 31 Jan 2007 10:56:53 +0100 [thread overview]
Message-ID: <8fe92b430701310156u958f6dau31552c636ba6bce2@mail.gmail.com> (raw)
In-Reply-To: <200701301950.00195.jnareb@gmail.com>
On 1/30/07, Jakub Narebski <jnareb@gmail.com> wrote:
> ...so "git clone" tries to checkout HEAD -> refs/heads/master
> branch, which does not exist. It is strange that git does not
> report error or at least warning, though...
It would be nice if git-clone at the very end (at checkout) wrote which
branch we are at, e.g.
"On branch refs/heads/master"
"Not currently on any branch"
"Current branch refs/heads/master does not exist"
--
Jakub Narebski
next prev parent reply other threads:[~2007-01-31 9:56 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
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 [this message]
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=8fe92b430701310156u958f6dau31552c636ba6bce2@mail.gmail.com \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=rael@zopyra.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 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).