git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Martin Langhoff <martin@catalyst.net.nz>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: git-cvsimport does not like detached HEAD
Date: Thu, 05 Apr 2007 09:40:18 +1200	[thread overview]
Message-ID: <46141B42.4080102@catalyst.net.nz> (raw)
In-Reply-To: <7vmz1pzx12.fsf@assigned-by-dhcp.cox.net>

Junio C Hamano wrote:
> In my day-job project, I use git-cvsimport with -i option to
> treat the central CVS repository as if it is just a branch in a
> remote git repository.  Since I hoard many changes in my git
> repository and trickle only a few changes at a time to the
> central CVS back, I keep shuffling and rebasing my commits on
> top of what I obtain from CVS, and many times, my HEAD is
> detached and not on a particular branch.

I don't quite understand detached HEAD very well so my reply may be
bogus... (I'm familiar with cg-seek, which seems to be a similar concept
of checking out an arbitrary commit in a mode where you are not allowed
to commit because you are not really at the tip of any branch).

> However, it seems git-cvsimport does not like to work when your
> HEAD is detached.

Yep - I can see how...

> Here is a minimum patch that seems to let me going, but I am not
> quite sure what the implication is for letting orig_branch (and
> last_branch) to default to "master" (I do not use "master"
> branch for that project so maybe I am getting lucky).

cvsimport should never write to 'master'*, so setting $last_branch to
master will mean that it will always switch to the branch it's importing
(and the switch will do the initialisation of temp index files, etc).
You could set it to '' and get the same effect, perhaps even safer.

* unless the cvs repo has a branch called 'master', and in that case
we're fsck'd.

Which leads me to think -- how magic is master anyway. Should we protect
it? The CVS repo could have a branchname collision with us on any
refname -- always make sure that repos where I do cvsimport are never
development repositories, which means that my dev branches are protected
from collisions. I think it's the only sane thing to do.

OTOH, it's trivial to say something like (warning, MUA-broken patch)

diff --git a/git-cvsimport.perl b/git-cvsimport.perl
index 1a1ba7b..73e0544 100755
--- a/git-cvsimport.perl
+++ b/git-cvsimport.perl
@@ -685,6 +685,9 @@ my (@old,@new,@skipped,%ignorebranch);
 # commits that cvsps cannot place anywhere...
 $ignorebranch{'#CVSPS_NO_BRANCH'} = 1;

+# protect 'master';
+$ignorebranch{'master'} = 1;
+
 sub commit {
        if ($branch eq $opt_o && !$index{branch} &&
!get_headref($branch, $git_dir)) {
            # looks like an initial commit


cheers,


m
-- 
-----------------------------------------------------------------------
Martin @ Catalyst .Net .NZ  Ltd, PO Box 11-053, Manners St,  Wellington
WEB: http://catalyst.net.nz/           PHYS: Level 2, 150-154 Willis St
OFFICE: +64(4)916-7224  UK: 0845 868 5733 ext 7224  MOB: +64(21)364-017
      Make things as simple as possible, but no simpler - Einstein
-----------------------------------------------------------------------

      reply	other threads:[~2007-04-04 22:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-03  8:23 git-cvsimport does not like detached HEAD Junio C Hamano
2007-04-04 21:40 ` Martin Langhoff [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=46141B42.4080102@catalyst.net.nz \
    --to=martin@catalyst.net.nz \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    /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).