From: Junio C Hamano <gitster@pobox.com>
To: Martin Langhoff <martin@catalyst.net.nz>
Cc: Marc-Andre Lureau <marcandre.lureau@gmail.com>, git@vger.kernel.org
Subject: Re: [PATCH] git-cvsimport: fix initial checkout
Date: Thu, 13 Mar 2008 16:15:17 -0700 [thread overview]
Message-ID: <7vr6eew70a.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <47D9A836.9010601@catalyst.net.nz> (Martin Langhoff's message of "Fri, 14 Mar 2008 11:18:30 +1300")
Martin Langhoff <martin@catalyst.net.nz> writes:
> Marc-Andre Lureau wrote:
>> git-symbolic-ref HEAD returns master reference, even if the file does
>> not exists. That prevents the initial checkout and fails in
>> git-rev-parse.
>
> But you are patching the block that gets triggered on subsequent
> imports, this code does not deal with "initial checkout" unless
> something else is wrong. The line right above the open() is an else that
> has the block that matters.
>
>> The patch checks the existence of the reference file
>> before assuming an original branch exists. There might be better
>> solutions than checking file existence.
>
> There are indeed. If we need this patch -- then you can call git
> ref-parse right to see if you get a sha1.
>
>> - unless ($last_branch) {
>> + if (-f "$git_dir/$last_branch") {
>
> Note that the file won't exist there in any modern git. It will be in
> $git_dir/refs/heads/$last_branch. Did you test this patch?
Martin, it may not even be in $git_dir/refs/heads/$last_branch ;-) The
refs can be packed.
By the way, doesn't cvsimport fail when your HEAD is detached with this
code?
I always have cvsimport update the pristine upstream branch and rebase my
work against it, so I never have the branch cvsimport updates checked
out, and for meit seems to work wonderfully (well, at least as wonderful
as a workflow that involves any CVS in it could be). I do not see a
reason why it should not to work similarly well when my HEAD is detached..
next prev parent reply other threads:[~2008-03-13 23:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-13 19:09 [PATCH] git-cvsimport: fix initial checkout Marc-Andre Lureau
2008-03-13 21:05 ` Junio C Hamano
2008-03-13 22:18 ` Martin Langhoff
2008-03-13 23:04 ` Marc-André Lureau
2008-03-13 23:07 ` Marc-André Lureau
2008-03-13 23:29 ` Martin Langhoff
2008-03-13 23:15 ` Junio C Hamano [this message]
2008-03-13 23:27 ` Martin Langhoff
2008-03-13 23:22 ` Marc-André Lureau
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=7vr6eew70a.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=marcandre.lureau@gmail.com \
--cc=martin@catalyst.net.nz \
/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).