From: Frank Lichtenheld <frank@lichtenheld.de>
To: Git Mailing List <git@vger.kernel.org>
Cc: Junio C Hamano <junkio@cox.net>
Subject: Various git-cvsserver patches
Date: Sun, 27 May 2007 14:33:05 +0200 [thread overview]
Message-ID: <1180269190126-git-send-email-frank@lichtenheld.de> (raw)
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 reply other threads:[~2007-05-27 12:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-27 12:33 Frank Lichtenheld [this message]
2007-05-27 12:33 ` [PATCH] cvsserver: Correct inetd.conf example in asciidoc documentation Frank Lichtenheld
2007-05-27 12:33 ` [PATCH] cvsserver: Note that CVS_SERVER can also be specified as method variable Frank Lichtenheld
2007-05-27 12:33 ` [PATCH] cvsserver: Fix some typos in asciidoc documentation Frank Lichtenheld
2007-05-27 12:33 ` [PATCH] t9400: Work around CVS' deficiencies Frank Lichtenheld
2007-05-27 12:33 ` [PATCH] cvsserver: Handle 'cvs login' Frank Lichtenheld
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1180269190126-git-send-email-frank@lichtenheld.de \
--to=frank@lichtenheld.de \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).