git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Martin Langhoff <martin.langhoff@gmail.com>
To: Alex Bennee <kernel-hacker@bennee.com>
Cc: git@vger.kernel.org
Subject: Re: Importing from CVS issues
Date: Tue, 16 Aug 2005 23:26:13 +1200	[thread overview]
Message-ID: <46a038f90508160426450eff12@mail.gmail.com> (raw)
In-Reply-To: <1124188894.7444.9.camel@okra.transitives.com>

I haven't seen this problem myself. There are some recent patches
Junio merged that handle some oddities better. Give the 'pu' branch a
go if you can.

I take it that the repo is not public. I'd like to try and reproduce
the problem. Can you get it to happen with a public repository?

For debugging, I'd say proofread the cvsps output, see ~/.cvsps/#repo
. that could give you hints as to the 'nameless' branches. Why is
origin missing is a different problem.

Ah! Important: if you're adding debugging statements by hand, bear in
mind that part of the code is executed in a forked child process, and
prints there will mess things up.

cheers,


martin

  reply	other threads:[~2005-08-16 11:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-16 10:41 Importing from CVS issues Alex Bennee
2005-08-16 11:26 ` Martin Langhoff [this message]
2005-08-16 16:09   ` Alex Bennee
2005-08-16 12:16 ` David Kågedal
2005-08-16 13:48   ` Alex Bennee

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=46a038f90508160426450eff12@mail.gmail.com \
    --to=martin.langhoff@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=kernel-hacker@bennee.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).