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

Re: parsecvs tool now creates git repositories

From
EMErik Mouw <erik@harddisk-recovery.com>
Date
Apr 3, 2006, 14:03 UTC
Message-ID
<20060403140348.GE16823@harddisk-recovery.com>
In-Reply-To
<1143956188.2303.39.camel@neko.keithp.com>
On Sat, Apr 01, 2006 at 09:36:28PM -0800, Keith Packard wrote:
Show 8 quoted lines
> The UI is a total disaster, sufficient for testing. You must create an
> Authors file in the current directory which looks like the git-cvsimport
> authors file. You must also have a edit-change-log program in your path
> which edits the commit message in place. /bin/true will work if you
> don't need to edit the messages.
> 
> I should clearly steal the existing git-cvsimport command line arguments
> and use those.

What is the current way to use it? I get the impression it reads raw ,v files, but how do I get along with a remote CVS repository?

Erik
-- 
+-- Erik Mouw -- www.harddisk-recovery.com -- +31 70 370 12 90 --
| Lab address: Delftechpark 26, 2628 XH, Delft, The Netherlands
Previous: Keith PackardNext: Jakub Narebski
Message 10 of 22 in “parsecvs tool now creates git repositories”
  1. Keith PackardApr 2, 2006
  2. Jan-Benedict GlawApr 2, 2006
  3. Jan-Benedict GlawApr 2, 2006
  4. Keith PackardApr 3, 2006
  5. Linus TorvaldsApr 3, 2006
  6. Jan-Benedict GlawApr 3, 2006
  7. Erik MouwApr 3, 2006
  8. Keith PackardApr 3, 2006
  9. Keith PackardApr 3, 2006
  10. Erik MouwApr 3, 2006
  11. Jakub NarebskiApr 3, 2006
  12. Keith PackardApr 3, 2006
  13. Keith PackardApr 3, 2006
  14. Jeff KingApr 3, 2006
  15. Anand KumriaApr 4, 2006
  16. Martin LanghoffApr 3, 2006
  17. Keith PackardApr 4, 2006
  18. Martin LanghoffApr 4, 2006
  19. Keith PackardApr 4, 2006
  20. Martin LanghoffApr 4, 2006
  21. Keith PackardApr 4, 2006
  22. Junio C HamanoApr 4, 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.