From: Martin Langhoff <martin.langhoff@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Stefan Karpinski <stefan.karpinski@gmail.com>, git@vger.kernel.org
Subject: Re: [PATCH] git-cvsserver: handle CVS 'noop' command.
Date: Fri, 30 Jan 2009 14:32:14 +1300 [thread overview]
Message-ID: <46a038f90901291732o56c19387w9debbdc5b2027904@mail.gmail.com> (raw)
In-Reply-To: <7v7i4denpg.fsf@gitster.siamese.dyndns.org>
On Fri, Jan 30, 2009 at 11:45 AM, Junio C Hamano <gitster@pobox.com> wrote:
> Not a no-brainer at all, sorry.
+1 on Junio's notes and patch.
Can someone with a real TortoiseCVS and a real cvs server sniff the
connection and catch the noop? (Can TortoiseCVS write debug logs of
the conversation with the server?)
Hysterical note: the original implementation of cvsserver was done
reading the output of `cvs -t $opts $cmd`, and ocassionally sniffing
the traffic on the wire or ssh connection.
Probably not a major issue for 'noop' though :-)
cheers,
m
--
martin.langhoff@gmail.com
martin@laptop.org -- School Server Architect
- ask interesting questions
- don't get distracted with shiny stuff - working code first
- http://wiki.laptop.org/go/User:Martinlanghoff
prev parent reply other threads:[~2009-01-30 1:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1232144521-21947-1-git-send-email-stefan.karpinski@gmail.com>
[not found] ` <1232144521-21947-2-git-send-email-stefan.karpinski@gmail.com>
2009-01-23 5:43 ` [PATCH] git-cvsserver: run post-update hook *after* update Stefan Karpinski
2009-01-23 8:00 ` Junio C Hamano
2009-01-29 21:58 ` Stefan Karpinski
2009-01-29 22:48 ` Junio C Hamano
2009-01-29 23:26 ` Stefan Karpinski
2009-01-29 22:56 ` Andy Parkins
2009-01-29 21:35 ` [PATCH] git-cvsserver: handle CVS 'noop' command Stefan Karpinski
2009-01-29 22:45 ` Junio C Hamano
2009-01-29 23:39 ` Stefan Karpinski
2009-01-29 23:46 ` Junio C Hamano
2009-01-30 1:12 ` Stefan Karpinski
2009-01-30 1:32 ` Martin Langhoff [this message]
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=46a038f90901291732o56c19387w9debbdc5b2027904@mail.gmail.com \
--to=martin.langhoff@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=stefan.karpinski@gmail.com \
/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).