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

Re: git-cvsimport fuzzy commit log matching?

From
CHChristoph Hellwig <hch@lst.de>
Date
Dec 23, 2008, 15:16 UTC
Message-ID
<20081223151643.GA18657@lst.de>
In-Reply-To
<46a038f90812230453m4122e018l2cc22be3f40ab630@mail.gmail.com>
On Tue, Dec 23, 2008 at 10:53:42AM -0200, Martin Langhoff wrote:
Show 9 quoted lines
> What you could do is
> 
>  1 - run cvsps with export to a file (I've posted in this list how to
> run it exactly as cvsimport does)
>  2 - post-process cvsps ouput with perl (there's a parser already in
> cvsimport ;-) )
>  3 - run cvsimport with the post-processed file
> 
> Or postprocess the imported git tree as others have suggested.

Instead of post-processing I hacked cvsps. It already has a different way to detect changesets when running in --bkcvs mode, and re-using that one for ptools works great.

Previous: Martin Langhoff
Message 4 of 4 in “git-cvsimport fuzzy commit log matching?”
  1. Christoph HellwigDec 23, 2008
  2. Pierre HabouzitDec 23, 2008
  3. Martin LanghoffDec 23, 2008
  4. Christoph HellwigDec 23, 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.