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

Re: parsecvs tool now creates git repositories

From
Martin Langhoff <martin.langhoff@gmail.com>
Date
Apr 6, 2006, 21:51 UTC
Message-ID
<46a038f90604061451m4522e3f3qceae2331751a307c@mail.gmail.com>
In-Reply-To
<1144354356.2303.270.camel@neko.keithp.com>
On 4/7/06, Keith Packard <keithp@keithp.com> wrote:
> > Almost all of the errors I was seeing in the last version were fixed
> > with your "branches that don't get merged back to the trunk" fix.
>
> That's good news at least.

I'm re-running my import of Moodle's cvs (20K commits) with the newer parsecvs. The previous attempt looked very good except that

 - file additions were recorded with one-commit-per-file. I am not
sure how rcs is recording these, but hte user does enter a common
message at "commit" time. Perhaps the file addition action could be
ignored then?
 - some tags made on a branch show up in HEAD. This may be due to
partial-tree branches, but I am not sure.
cheers
m
Previous: Keith PackardNext: Keith Packard
Message 10 of 13 in “Fixes to parsecvs”
  1. Keith PackardApr 6, 2006
  2. Jan-Benedict GlawApr 6, 2006
  3. Keith PackardApr 6, 2006
  4. Johannes SchindelinApr 6, 2006
  5. Jan-Benedict GlawApr 6, 2006
  6. Keith PackardApr 6, 2006
  7. Francois RomieuApr 9, 2006
  8. Jim RadfordApr 6, 2006
  9. Keith PackardApr 6, 2006
  10. Martin LanghoffApr 6, 2006
  11. Keith PackardApr 6, 2006
  12. Martin LanghoffApr 6, 2006
  13. Keith PackardApr 7, 2006

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.