mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrea Arcangeli <andrea@suse.de>
To: David Mansfield <david@cobite.com>
Cc: David Mansfield <lkml@dm.cobite.com>, linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] cvsps support for parsing BK->CVS kernel tree logs
Date: Thu, 20 Mar 2003 02:00:32 +0100	[thread overview]
Message-ID: <20030320010032.GX30541@dualathlon.random> (raw)
In-Reply-To: <Pine.LNX.4.44.0303191837360.19298-100000@admin>

On Wed, Mar 19, 2003 at 07:19:32PM -0500, David Mansfield wrote:
> On Wed, 19 Mar 2003, Andrea Arcangeli wrote:
> 
> > this is a critical feature for me, note that if Larry agreed of tagging
> > the tree with the atomic-date of the patchset extracting those patchset
> > would be an order of magnitude faster, I would pay for the RTT latency 1
> > per patchset, not once per file and it would be possible to teach cvsps
> > to learn diffing against the tag if it matches. Anyways stuff works now
> > so I'll just wait for the RTT all the time w/o being able to use the
> > real bandwidth provided by my link. As soon as the CVS tarball is
> > available I'll use it for the large patch extractions.
> 
> I just looked briefly at the 'cvs server' protocol.  It looks fairly easy 
> to have a 'keepalive' session with a server where multiple diffs of 
> multiple files are requested.  This isn't a 5 minute fix though, but I've 

this sounds an excellent plan if technically doable

> been bothered by the RTT per file as well, because we use 'ssh' to 
> authenticate cvs access here, and each file is a complete ssh handshake 
> which is very slow.

with ssh the latency would be exploded indeed, it takes quite some cpu too

> > One more feature wish (besides the python inteface for a quick gui) is
> > the C^c killing cvsps too during a -g patch extraction, you probably
> > should check the return code of cvs when extracting the patches. Right
> > now I press C^z and then I killall cvsps ;)
> 
> Already fixed in my code.  I won't bother you with a diff.

I'll fetch it with the next release, thanks.

Andrea

      reply	other threads:[~2003-03-20  0:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-18 17:41 David Mansfield
2003-03-19 20:11 ` Andrea Arcangeli
2003-03-19 21:19   ` David Mansfield
2003-03-19 21:37     ` Andrea Arcangeli
2003-03-19 22:21       ` David Mansfield
2003-03-19 22:40         ` Andrea Arcangeli
2003-03-19 22:36       ` Andrea Arcangeli
2003-03-20  0:19         ` David Mansfield
2003-03-20  1:00           ` Andrea Arcangeli [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=20030320010032.GX30541@dualathlon.random \
    --to=andrea@suse.de \
    --cc=david@cobite.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@dm.cobite.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

all inboxes | Powered by JetHome®