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

Re: CVS to git: parsing ChangeLog entries?

From
Michael Haggerty <mhagger@alum.mit.edu>
Date
Mar 14, 2008, 18:40 UTC
Message-ID
<47DAC6A1.7070400@alum.mit.edu>
In-Reply-To
<20080312190827.GE3198@ins.uni-bonn.de>

I'll answer your questions from the point of view of cvs2git, a.k.a. cvs2svn (http://cvs2svn.tigris.org).

Ralf Wildenhues wrote:
Show 8 quoted lines
> when migrating a project that uses GNU-style ChangeLogs from CVS
> to git, is it possible to extract patch author information from
> the ChangeLog entries rather than from the CVS commit logs?
> For simplicity let's first assume the project used only one
> ChangeLog file.
> 
> Asking because it is not uncommon that patches are committed on
> behalf of other people, and it would be nice to credit them.

There is no builtin support for this in cvs2git. But the place where the author is determined knows about the whole changeset, including any simultaneous changes to the changelog. So it should be possible to add this functionality without too much work.

> Related question: when CVS commit logs have varying encoding,
> say, some latin1 and some UTF-8, is it possible to have uniformly
> encoded git log entries?

cvs2git allows you to specify multiple encodings. It tries one after the other until one works successfully. It also has hooks where you can add your own decoder using arbitrary Python code.

That reminds me that there is a Python universal decoder that uses heuristics to determine the encoding of an arbitrary octet stream. That might be a nice thing to add support for....

Michael
Previous: Ralf Wildenhues
Message 4 of 4 in “CVS to git: parsing ChangeLog entries?”
  1. Ralf WildenhuesMar 12, 2008
  2. Jeff KingMar 13, 2008
  3. Ralf WildenhuesMar 15, 2008
  4. Michael HaggertyMar 14, 2008

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.