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
Frank Lichtenheld <frank@lichtenheld.de>
Date
Jun 17, 2007, 17:20 UTC
Message-ID
<20070617172041.GF1828@planck.djpig.de>
In-Reply-To
<46756707.5020805@tobit.co.uk>
On Sun, Jun 17, 2007 at 05:53:27PM +0100, Dirk Koopman wrote:
Show 10 quoted lines
> Frank Lichtenheld wrote:
> >Summary: You're (ab)using cvsserver in very interesting ways that are not
> >really beeing thought of in the current design/implementation. There'll
> >be dragons ;)
> >
> 
> Hmm... I think that is becoming clear. The trouble is that I am not at 
> all certain that what I am doing is particularly unusual. After all, 
> using git, the whole point is that working on branches or the main line 
> should easy and cheap!

Sure, it is a know limitation of cvsserver. But it is not trivially to remove. Patches welcome ;)

Gruesse,
-- 
Frank Lichtenheld <frank@lichtenheld.de>
www: http://www.djpig.de/
Previous: Dirk KoopmanNext: Martin Langhoff
Message 6 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.