linux-kernel - Re: Git pull ack emails..

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: <CACRpkdbi2gqqc271eMgHjD68bqf2mzw8zw+iAhYv2LFajfo-eQ@mail.gmail.com>
Date:   Tue, 23 Oct 2018 10:53:25 +0200
From:   Linus Walleij <linus.walleij@...aro.org>
To:     Linus Torvalds <torvalds@...ux-foundation.org>
Cc:     Boris Brezillon <boris.brezillon@...tlin.com>,
        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>, Mark Brown <broonie@...nel.org>,
        Ulf Hansson <ulf.hansson@...aro.org>,
        Greg KH <gregkh@...uxfoundation.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: Git pull ack emails..

On Tue, Oct 23, 2018 at 10:41 AM Linus Torvalds
<torvalds@...ux-foundation.org> wrote:

> In particular, the issue is that after each pull, I do a build test
> before the pull is really "final", and while that build test is
> ongoing (which takes anything from a few minutes to over an hour when
> I'm on the road and using my laptop), I go on and look at the *next*
> pull (or one of the other pending ones).

So that is how you work, we have mental models about
how the upstream maintainers workflow is done but always
guessed it was something like this, nice to know.

> Comments?

I don't need the ACKs becuase there is just always some reason or
nervousness that make me sit and git pull --ff-only all the time during
the merge window because I worry that something will break on mine
or others machines.

Can't you just tool something that mails automatically after-the-fact?
Greg's "notices" that patch so or so was applied are clearly
auto-generated by a script after he applied and tested a whole
bunch of them, the same should be possible for pull requests
methinks? Just something you run after a workday sealing the
deal.

Linus Walleij