From: Michael Haggerty <mhagger@alum.mit.edu>
To: Prenom Nom <utilisateur_768@yahoo.fr>
Cc: git@vger.kernel.org
Subject: Re: git-cvsimport : fatal: 'Root_branche_2_0_*_' is not a valid tag name.
Date: Thu, 12 Feb 2009 10:32:24 +0100 [thread overview]
Message-ID: <4993ECA8.9000900@alum.mit.edu> (raw)
In-Reply-To: <4993CF2C.6010704@yahoo.fr>
Prenom Nom wrote:
> i'd like to import a project from CVS.
If you can do this as a one-time conversion, please consider using
cvs2git [1].
> The cvs commits are done using
> Cp1252 encoding charset. The thing is i cannot change the .git/config
> file since the repo is created by git-cvsimport. So how can i use the
> good charset ?
cvs2git can convert the encoding of filenames, log messages, and author
names during the conversion.
> during a run of git-cvsimport, i got this error :
> fatal: 'Root_branche_2_0_*_' is not a valid tag name.
> Cannot create tag Root_branche_2_0_*_: Bad file descriptor
cvs2git can arbitrarily transform tag and branch names during the
conversion via user-specified transformation rules.
> I can't use -p -b xxx since i would like to test branch merging in git
> so i need HEAD AND some CVS branch (you can't use -b 2 times for cvsps).
>
> So i guess i won't be able to test git branch merging...
Long-term synchronization between CVS and git is fragile. Consider
converting to git altogether. If that is not possible for political or
technical reasons, consider converting your repository to Subversion
(IMHO a no-brainer in even the most conservative shop), then using
git-svn as a git-to-Subversion bridge (it is much more reliable than
git-to-CVS).
Michael
[1] http://cvs2svn.tigris.org/cvs2git.html
prev parent reply other threads:[~2009-02-12 9:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-12 7:26 git-cvsimport : fatal: 'Root_branche_2_0_*_' is not a valid tag name Prenom Nom
2009-02-12 9:32 ` Michael Haggerty [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=4993ECA8.9000900@alum.mit.edu \
--to=mhagger@alum.mit.edu \
--cc=git@vger.kernel.org \
--cc=utilisateur_768@yahoo.fr \
/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).