git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: git-cvsimport : fatal: 'Root_branche_2_0_*_' is not a valid tag name.

From
Michael Haggerty <mhagger@alum.mit.edu>
Date
Feb 12, 2009, 09:32 UTC
Message-ID
<4993ECA8.9000900@alum.mit.edu>
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
Previous: Prenom Nom
Message 2 of 2 in “git-cvsimport : fatal: 'Root_branche_2_0_*_' is not a valid tag name.”
  1. Prenom NomFeb 12, 2009
  2. Michael HaggertyFeb 12, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.