From: Francis Galiegue <fg@one2team.net>
To: git@vger.kernel.org
Subject: git-cvsimport bug? Newly created branch not seen unless there's at least one commit in it
Date: Thu, 23 Oct 2008 14:01:09 +0200 [thread overview]
Message-ID: <200810231401.09262.fg@one2team.net> (raw)
Hello,
I've tried to git-cvsimport a module from CVS, where a branch named "foo"
existed. CVSROOT set in the environment, CVS_RSH too, and I imported with:
git-cvsimport -k -a -C themodule themodule
However, it didn't do what I expected: I couldn't see the branch named "foo".
I had to make a commit using CVS on that very same module on that "foo"
branch. After the commit, out of curiosity, I executed the same git command
again in the same directory: this time the branch was seen.
Is this a bug, or is there a git-cvsimport option that I missed? I have looked
at the manpage several times, and couldn't find what option could be of any
use in my case (mind you, I haven't looked at the cvsps manpage either).
Thanks,
--
fge
next reply other threads:[~2008-10-23 12:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-23 12:01 Francis Galiegue [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-10-23 12:00 git-cvsimport bug? Newly created branch not seen unless there's at least one commit in it Francis Galiegue
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=200810231401.09262.fg@one2team.net \
--to=fg@one2team.net \
--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;
as well as URLs for NNTP newsgroup(s).