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

Re: Pointers to CVS 2 GIT imports and gateways

From
Martin Langhoff <martin.langhoff@gmail.com>
Date
May 9, 2005, 05:41 UTC
Message-ID
<46a038f905050822413ece89b9@mail.gmail.com>
In-Reply-To
<427EEB9E.9070701@zytor.com>
On 5/9/05, H. Peter Anvin <hpa@zytor.com> wrote:
> What would be the point?  The reason for bkcvs was that bk wasn't
> available to everyone.

Ease of transition for other automated tasks, perhaps? I don't know what bits and pieces of infrastructure hang from the old BK-CVS changeset distribution infrastructure.

Some projects do count on CVS gateways even if they use smarter SCMs. This is not just because of licensing issues -- sometimes portability and preexisting tools trump SCM changes.

regards,
martin
Previous: H. Peter AnvinNext: H. Peter Anvin
Message 3 of 4 in “Pointers to CVS 2 GIT imports and gateways”
  1. Martin LanghoffMay 8, 2005
  2. H. Peter AnvinMay 9, 2005
  3. Martin LanghoffMay 9, 2005
  4. H. Peter AnvinMay 9, 2005

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.