From: "David Symonds" <dsymonds@gmail.com>
To: "Sergei Organov" <osv@javad.com>
Cc: git@vger.kernel.org
Subject: Re: git clone through http bug?
Date: Thu, 14 Feb 2008 09:36:22 -0800 [thread overview]
Message-ID: <ee77f5c20802140936y28be9b39i59753af66e1a5e36@mail.gmail.com> (raw)
In-Reply-To: <873arvv479.fsf@osv.gnss.ru>
On Thu, Feb 14, 2008 at 9:27 AM, Sergei Organov <osv@javad.com> wrote:
> Hello,
>
> I've just cloned the public repo (it's rather small):
>
> $ git clone http://ydirson.free.fr/soft/git/cvsps.git
>
> and it has created cvsps/.git, but no working copy.
That's because the remote side doesn't have a HEAD. Just run "git
checkout --track -b master origin/master" to create a local branch the
tracks the origin/master branch.
Dave.
next prev parent reply other threads:[~2008-02-14 17:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-14 17:27 git clone through http bug? Sergei Organov
2008-02-14 17:36 ` David Symonds [this message]
2008-02-14 18:28 ` Sergei Organov
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=ee77f5c20802140936y28be9b39i59753af66e1a5e36@mail.gmail.com \
--to=dsymonds@gmail.com \
--cc=git@vger.kernel.org \
--cc=osv@javad.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).