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
Andreas Schwab <schwab@linux-m68k.org>
Date
Dec 10, 2010, 19:58 UTC
Message-ID
<m2ei9p8knw.fsf@igel.home>
In-Reply-To
<20101209220347.GA3180@shuttle.home>
Thomas Adam <thomas@xteddy.org> writes:
Show 8 quoted lines
> 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.

The cvsps output is ambigous. If the commit log includes text that resembles the patchset format generated by cvsps then git-cvsimport can easily get confused.

Andreas.
-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."
Previous: Michael J Gruber
Message 3 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.