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

Various git-cvsserver patches

From
Frank Lichtenheld <frank@lichtenheld.de>
Date
May 27, 2007, 12:33 UTC
Message-ID
<1180269190126-git-send-email-frank@lichtenheld.de>
Frank Lichtenheld (5):
      cvsserver: Correct inetd.conf example in asciidoc documentation
      cvsserver: Note that CVS_SERVER can also be specified as method variable
      cvsserver: Fix some typos in asciidoc documentation
      t9400: Work around CVS' deficiencies
      cvsserver: Handle 'cvs login'
 Documentation/git-cvsserver.txt |   27 ++++++++++++++++++---------
 git-cvsserver.perl              |    8 +++++---
 t/t9400-git-cvsserver-server.sh |   33 +++++++++++++++++++++++++++++++--
 3 files changed, 54 insertions(+), 14 deletions(-)

The first three patches are some fixes/improvements to the asciidoc documentation. Just some random stuff that I noticed while working on git-cvsserver.

The forth one is a good example how much CVS actually sucks regarding data security and deterministic behaviour.

All of these should be suitable for maint.

The fifth is a small feature enhancement for git-cvsserver. It adds support for 'cvs login' over pserver.

I think this is trivial enough to go to master directly, but feel free to let it rot in next first.

Next: Frank Lichtenheld
Message 1 of 6 in “Various git-cvsserver patches”
  1. Frank LichtenheldMay 27, 2007
  2. cvsserver: Correct inetd.conf example in asciidoc documentationFrank Lichtenheld, May 27, 2007
  3. cvsserver: Note that CVS_SERVER can also be specified as method variableFrank Lichtenheld, May 27, 2007
  4. cvsserver: Fix some typos in asciidoc documentationFrank Lichtenheld, May 27, 2007
  5. t9400: Work around CVS' deficienciesFrank Lichtenheld, May 27, 2007
  6. cvsserver: Handle 'cvs login'Frank Lichtenheld, May 27, 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.