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

Re: [PATCH] cvsserver: fix legacy cvs client and branch rev issues

From
Martin Langhoff <martin.langhoff@gmail.com>
Date
Jun 17, 2007, 21:27 UTC
Message-ID
<46a038f90706171427g43c4ccf2vdf1172a962481964@mail.gmail.com>
In-Reply-To
<20070617103744.GE1828@planck.djpig.de>
On 6/17/07, Frank Lichtenheld <frank@lichtenheld.de> wrote:
Show 12 quoted lines
> On Sun, Jun 17, 2007 at 10:10:51AM +0100, Dirk Koopman wrote:
> > Frank Lichtenheld wrote:
> > >On Sat, Jun 16, 2007 at 07:50:06PM +0100, Dirk Koopman wrote:
> > >Hmm, I don't see how you could have a problem with that since cvsserver
> > >doesn't support branches and never generates any revision numbers in
> > >that format?
> > >
> > >There is probably much more code out there in cvsserver that does assume
> > >that revision is always a simple integer.
>
> Let me rephrase that (after actually looking through the code):
> All of the revision handling code assumes that.

Exactly. cvsserver emulates CVS on a single HEAD, that's why you use the headname as the 'module' parameter you pass to CVS when doing a checkout.

...
Show 5 quoted lines
> Hmm, so you did the cvs update in an old working copy of the original
> CVS repository? Then CVS sent those version numbers from the CVS/Entries
> file to the server, cvsserver certainly never generates numbers like
> that. And I would be very suprised if you could do anything remotely
> useful with abusing the old working copy this way...
Agreed - that's not really supported.

Now, I'd _love_ to have a bit of time to implement CVS-style branch support to cvsserver (so a check for valid version numbers that have more dots would be a good thing), but it's hard hard hard, specially because there are many ambiguities to resolve. It would enormously useful to have branch support together with support for a bit of "version skew" so that you can replace a real CVS server with cvsserver and have people continue using the old cvs checkouts -- because the file versions and branches match.

As things stand, I want to say thanks to Frank for giving cvsserver some love :-)

cheers,
martin
Previous: Frank LichtenheldNext: Frank Lichtenheld
Message 7 of 8 in “cvsserver: fix legacy cvs client and branch rev issues”
  1. cvsserver: fix legacy cvs client and branch rev issuesDirk Koopman, Jun 16, 2007
  2. Frank LichtenheldJun 17, 2007
  3. Dirk KoopmanJun 17, 2007
  4. Frank LichtenheldJun 17, 2007
  5. Dirk KoopmanJun 17, 2007
  6. Frank LichtenheldJun 17, 2007
  7. Martin LanghoffJun 17, 2007
  8. cvsserver: always initialize state in argsplit()Frank Lichtenheld, Jun 17, 2007

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.