[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20181023111738.7f50e2bd@bbrezillon>
Date: Tue, 23 Oct 2018 11:17:38 +0200
From: Boris Brezillon <boris.brezillon@...tlin.com>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Catalin Marinas <catalin.marinas@....com>,
Christoph Hellwig <hch@....de>,
Guenter Roeck <linux@...ck-us.net>,
Jacek Anaszewski <jacek.anaszewski@...il.com>,
Jens Axboe <axboe@...nel.dk>,
Linus Walleij <linus.walleij@...aro.org>,
Mark Brown <broonie@...nel.org>,
Ulf Hansson <ulf.hansson@...aro.org>,
Greg KH <gregkh@...uxfoundation.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Git pull ack emails..
Hi Linus,
On Tue, 23 Oct 2018 09:41:32 +0100
Linus Torvalds <torvalds@...ux-foundation.org> wrote:
> So I'm mainly pinging people I've already pulled to see how much
> people actually _care_. Yes, the ack is nice, but do people care
> enough that I should try to make that workflow change? Traditionally,
> you can see that I've pulled from just seeing the end result when it
> actually hits the public tree (which is yet another step removed from
> the steps above - I do build tests between every pull, but I generally
> tend to push out the end result in batches, usually a couple of times
> a day).
>
> Comments?
I do like to receive notifications when a PR is merged (or when a patch
or patchset is applied). Note that I don't care if this notification is
sent in-reply to the original email or in a separate email. I know Mark
(Brown) has it automated in some way, not sure if it's through patchwork
or if he's using a custom tool, and I'm also not sure it works for pull
requests.
Anyway, it's just a nice thing to have, and I can do without it if it's
too complicated to automate.
Regards,
Boris
Powered by blists - more mailing lists