From: "Thomas Hühn" <newsgroups@thomas-huehn.de>
To: git@vger.kernel.org
Subject: Re: git cvsimport fails
Date: Sun, 06 May 2007 09:04:38 +0200 [thread overview]
Message-ID: <87ejlu1lh5.fsf@mid.thomas-huehn.de> (raw)
In-Reply-To: 87lkg2v4ha.fsf@mid.deneb.enyo.de
Florian Weimer <fw@deneb.enyo.de> writes:
> * Thomas Hühn:
>
>> HEAD contains "ref: refs/heads/master", but refs/heads contains no
>> "master", just other files.
>>
>> Can I find out, which hash master should point at?
>
> After the initial checkout, it should point to "origin"; this is the
> HEAD of the CVS repository. Of course, if your main development line
> resides on another branch, you should use that.
Okay, thanks. I'll enter that.
Thomas
prev parent reply other threads:[~2007-05-06 7:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-01 15:47 git cvsimport fails Thomas Hühn
2007-05-01 15:54 ` Thomas Hühn
2007-05-06 6:41 ` Florian Weimer
2007-05-06 7:04 ` Thomas Hühn [this message]
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=87ejlu1lh5.fsf@mid.thomas-huehn.de \
--to=newsgroups@thomas-huehn.de \
--cc=git@vger.kernel.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