netdev - Re: patchwork for netdev

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.64.0809181706200.18136@shark.he.net>
Date:	Thu, 18 Sep 2008 17:09:14 -0700 (PDT)
From:	"Randy.Dunlap" <rdunlap@...otime.net>
To:	David Miller <davem@...emloft.net>
cc:	rdunlap@...otime.net, netdev@...r.kernel.org, jeff@...zik.org,
	linville@...driver.com
Subject: Re: patchwork for netdev

On Thu, 18 Sep 2008, David Miller wrote:

> From: "Randy.Dunlap" <rdunlap@...otime.net>
> Date: Thu, 18 Sep 2008 17:01:52 -0700 (PDT)
> 
> > Maybe patchwork for wireless would satisfy one of my concerns,
> > but it would be nice if John would ack patches like DaveM and Jeff do... :)
> 
> It's so much less work for me to click a bunch of buttons on a web
> page and work in batch mode, than it is to give personalized
> responses.  When you're applying 40, 50 patches in a day, every minute
> in the workflow starts to count.

Yes, understood.

> 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.

Thanks,
-- 
~Randy
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html