All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jamie Lokier <jamie@shareable.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] An organizational suggestion
Date: Tue, 3 Jun 2008 20:26:51 +0100	[thread overview]
Message-ID: <20080603192651.GD6899@shareable.org> (raw)
In-Reply-To: <18501.25321.636839.502256@mariner.uk.xensource.com>

Ian Jackson wrote:
> Jamie Lokier writes ("Re: [Qemu-devel] An organizational suggestion"):
> > It's the Linus Torvalds school of flow control.  If you don't get a
> > reply, try again.
> 
> I see.  That seems rather rude to me, so I don't do it.  Am I really
> supposed to keep a list of my outstanding patches and retransmit them
> like some kind of bandwidth-hogging peer-to-peer application ?

Exponential backoff - find the natural pace others can work at.  You
don't have to be a bandwidth hog :-)  But I was joking.  For the Linux
kernel, Linus has said that's what _he_ prefers, back in the days
before Git, but I don't know what's preferred here.

Some patches get a good response quickly, just look at recent threads.

I would guess it depends on which subsystem and whether it's in the
areas of interest of currently active developer-commiters.

> Also - implicit in your comment that it's a form of `flow control' is
> that it's caused by a lack of upstream capacity.  I think that part is
> very true.  We do have a lack of capacity, which can be solved in this
> case by adding one or more people I think.

Perhaps.  It's not necessarily easy to do that well.

-- Jamie

  parent reply	other threads:[~2008-06-03 19:26 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-03  5:42 [Qemu-devel] An organizational suggestion Balazs Attila-Mihaly (Cd-MaN)
2008-06-03  9:27 ` Ian Jackson
2008-06-03 10:00   ` Jamie Lokier
2008-06-03 10:19     ` Ian Jackson
2008-06-03 11:03       ` Jamie Lokier
2008-06-03 12:32         ` Ian Jackson
2008-06-03 13:01           ` [Qemu-devel] " Jan Kiszka
2008-06-03 14:26             ` Jamie Lokier
2008-06-03 22:24           ` [Qemu-devel] " Anthony Liguori
2008-06-03 13:45       ` Johannes Schindelin
2008-06-03 14:02         ` Ian Jackson
2008-06-03 14:35           ` Paul Brook
2008-06-03 14:41             ` Jamie Lokier
2008-06-03 14:55               ` Paul Brook
2008-06-03 15:14                 ` Jamie Lokier
2008-06-03 14:54             ` Laurent Vivier
2008-06-03 15:04             ` Ian Jackson
2008-06-03 15:17               ` Jamie Lokier
2008-06-03 15:27                 ` Ian Jackson
2008-06-03 16:54                   ` Anthony Liguori
2008-06-03 19:26                   ` Jamie Lokier [this message]
2008-06-03 15:24               ` Laurent Vivier
2008-06-03 20:37               ` Anthony Liguori
2008-06-03 20:27           ` Anthony Liguori
2008-06-03 10:23     ` Andreas Färber
2008-06-03 11:09       ` [Qemu-devel] " Jan Kiszka
2008-06-03 12:36         ` Ian Jackson
2008-06-03 12:48           ` Daniel P. Berrange
  -- strict thread matches above, loose matches on Subject: below --
2008-06-03 10:11 [Qemu-devel] " Balazs Attila-Mihaly (Cd-MaN)
2008-06-03 15:36 Balazs Attila-Mihaly (Cd-MaN)
2008-06-03 16:59 ` Andreas Färber

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=20080603192651.GD6899@shareable.org \
    --to=jamie@shareable.org \
    --cc=qemu-devel@nongnu.org \
    /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.