netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: "Randy.Dunlap" <rdunlap@xenotime.net>
Cc: David Miller <davem@davemloft.net>,
	netdev@vger.kernel.org, jeff@garzik.org, linville@tuxdriver.com
Subject: Re: patchwork for netdev
Date: Fri, 19 Sep 2008 03:13:07 -0400	[thread overview]
Message-ID: <20080919071307.GA22242@infradead.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0809181706200.18136@shark.he.net>

On Thu, Sep 18, 2008 at 05:09:14PM -0700, Randy.Dunlap wrote:
> > I was hoping those ACK emails would be one of the things I could stop
> > doing if patchwork is effective.  Not immediately, but eventually.
> 
> Well, that's a reasonable goal.  OTOH, if everyone wants to know
> if their patch was applied, then having 50 people look at a web page
> (or at a git tree) is more total overhead than one person generating
> an email.  IMHO.  But maybe it depends on which side is being optimized.

Could patchworks please generate the ACK mail automatically? 


  parent reply	other threads:[~2008-09-19  7:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-18 23:56 patchwork for netdev David Miller
2008-09-19  0:01 ` Randy.Dunlap
2008-09-19  0:05   ` David Miller
2008-09-19  0:09     ` Randy.Dunlap
2008-09-19  0:12       ` David Miller
2008-09-19  0:13         ` Randy.Dunlap
2008-09-19  7:13       ` Christoph Hellwig [this message]
2008-09-19  0:28     ` Rick Jones
2008-09-19  2:11       ` David Miller
2008-09-23  1:08         ` Simon Horman
2008-09-23  2:44           ` David Miller
2008-09-23  8:24             ` Benjamin Herrenschmidt
2008-09-23 10:44               ` Jeremy Kerr

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=20080919071307.GA22242@infradead.org \
    --to=hch@infradead.org \
    --cc=davem@davemloft.net \
    --cc=jeff@garzik.org \
    --cc=linville@tuxdriver.com \
    --cc=netdev@vger.kernel.org \
    --cc=rdunlap@xenotime.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).