From: Damien Diederen <dash@foobox.net>
To: Martin Langhoff <martin@catalyst.net.nz>,
Frank Lichtenheld <frank@lichtenheld.de>
Cc: git@vger.kernel.org
Subject: [PATCH 0/7] Enhance TkCVS interoperability
Date: Mon, 24 Mar 2008 23:48:39 +0100 [thread overview]
Message-ID: <cover.1206393086.git.dash@foobox.net> (raw)
This series was developed to improve interoperability between
git-cvsserver and TkCVS, a CVS client that is fairly popular at least
in some corporate environments.
Patches 1-6 are "obvious" improvements, implementing missing features
or fixing incorrect behaviour. 7 is more questionable, but likely to
result in more intelligible log output in a majority of cases.
Bear in mind that my perl-fu is not very high when reviewing this
series; suggestions are more than welcome!
Damien
Damien Diederen (7):
cvsserver: Respond to the 'editors' command.
cvsserver: Only print the file part of filename in status header.
cvsserver: Do not include status output for subdirectories if -l is
passed.
cvsserver: Add a few tests for 'status' command.
cvsserver: Implemented update -p (print to stdout)
cvsserver: Added test for update -p
cvsserver: Use the user part of the email in log and annotate results
git-cvsserver.perl | 67 ++++++++++++++++++++++++++++++--------
t/t9400-git-cvsserver-server.sh | 50 +++++++++++++++++++++++++++++
2 files changed, 103 insertions(+), 14 deletions(-)
next reply other threads:[~2008-03-24 22:49 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-24 22:48 Damien Diederen [this message]
2008-03-24 22:48 ` [PATCH 1/7] cvsserver: Respond to the 'editors' command Damien Diederen
2008-03-25 9:03 ` Frank Lichtenheld
2008-03-24 22:49 ` [PATCH 2/7] cvsserver: Only print the file part of the filename in status header Damien Diederen
2008-03-24 22:49 ` [PATCH 3/7] cvsserver: Do not include status output for subdirectories if -l is passed Damien Diederen
2008-03-24 22:50 ` [PATCH 4/7] cvsserver: Add a few tests for 'status' command Damien Diederen
2008-03-24 22:50 ` [PATCH 5/7] cvsserver: Implemented update -p (print to stdout) Damien Diederen
2008-03-24 22:50 ` [PATCH 6/7] cvsserver: Added test for update -p Damien Diederen
2008-03-24 22:50 ` [PATCH 7/7] cvsserver: Use the user part of the email in log and annotate results Damien Diederen
2008-03-25 9:26 ` Frank Lichtenheld
2008-03-25 9:39 ` Rafael Garcia-Suarez
2008-03-25 13:58 ` Damien Diederen
2008-03-25 1:08 ` [PATCH 0/7] Enhance TkCVS interoperability Junio C Hamano
2008-03-27 22:17 ` [PATCH v2 " Damien Diederen
2008-03-28 7:52 ` Junio C Hamano
2008-03-27 22:17 ` [PATCH v2 1/7] cvsserver: Respond to the 'editors' and 'watchers' commands Damien Diederen
2008-03-27 22:17 ` [PATCH v2 2/7] cvsserver: Only print the file part of the filename in status header Damien Diederen
2008-03-27 22:17 ` [PATCH v2 3/7] cvsserver: Do not include status output for subdirectories if -l is passed Damien Diederen
2008-03-27 22:18 ` [PATCH v2 4/7] cvsserver: Add a few tests for 'status' command Damien Diederen
2008-03-27 22:18 ` [PATCH v2 5/7] cvsserver: Implement update -p (print to stdout) Damien Diederen
2008-03-27 22:18 ` [PATCH v2 6/7] cvsserver: Add test for update -p Damien Diederen
2008-03-27 22:18 ` [PATCH v2 7/7] cvsserver: Use the user part of the email in log and annotate results Damien Diederen
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=cover.1206393086.git.dash@foobox.net \
--to=dash@foobox.net \
--cc=frank@lichtenheld.de \
--cc=git@vger.kernel.org \
--cc=martin@catalyst.net.nz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.