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

Re: git-cvsimport with cvsps output in commit msg breaks imports

From
Michael J Gruber <git@drmicha.warpmail.net>
Date
Dec 10, 2010, 12:48 UTC
Message-ID
<4D0221A3.6080706@drmicha.warpmail.net>
In-Reply-To
<20101209220347.GA3180@shuttle.home>
Thomas Adam venit, vidit, dixit 09.12.2010 23:03:
Show 26 quoted lines
> Hi all,
> 
> [ I've Cced both the cvsps maintainer and the author listed for
> git-cvsimport in case it's more relevant to either tool. ]
> 
> I am wondering if anyone here is able to shed some light on a problem I've
> encountered with git-cvsimport.  For ages now, I've had an automatic
> conversion of a CVS repository to a Git one, using git-cvsimport to update a
> repository as commits happen in CVS.
> 
> The repository in question is here:
> 
> https://github.com/ThomasAdam/tmux
> 
> Everything is on the Master branch.
> 
> More specifically, the commit which I think introduced the problem, and all
> subsequent commits thereafter is here:
> 
> https://github.com/ThomasAdam/tmux/commit/f0220a10b01a764e0dc52ea1b2407f58600a30eb
> 
> Note that from this commit onwards, the commit *message* has a bunch of
> cvsps output in it.  I can only surmise that this somehow causes problems
> for cvsimport.
> 
> But I can't say for sure.

The previous one has cvsps info in the commit message already, prefixed with "|". So the problem is the previous one or the one before.

If you have cvs checkout, can spot anything between those? Can you redo the cvsps import from that point on and check cvsps log?

Michael
Previous: Thomas AdamNext: Andreas Schwab
Message 2 of 3 in “git-cvsimport with cvsps output in commit msg breaks imports”
  1. Thomas AdamDec 9, 2010
  2. Michael J GruberDec 10, 2010
  3. Andreas SchwabDec 10, 2010

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.