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: <20181023200408.GA13179@chatter.qube.local>
Date:   Tue, 23 Oct 2018 16:04:08 -0400
From:   Konstantin Ryabitsev <konstantin@...uxfoundation.org>
To:     Linus Torvalds <torvalds@...ux-foundation.org>
Cc:     kirill@...temov.name, Linus Walleij <linus.walleij@...aro.org>,
        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 Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Git pull ack emails..

On Tue, Oct 23, 2018 at 10:46:06AM +0100, Linus Torvalds wrote:
>If it's a "proper" pull request (ie done by git request-pull), then
>the magic marker would be that it as that
>
>    for you to fetch changes up to %H:
>
>line where %H is the hash of the tip of the tree that is requested to be pulled.
>
>Then automation could literally just check "is that commit in Linus'
>public tree", and when that happens, generate an automatic
>notification that the pull request in question has been merged.

I can probably do something like that at kernel.org. How about something 
more generic -- e.g. a simple tool that asks a remote web service to 
notify you when a commit-id is seen in one of the kernel.org repos?

E.g.:

git lmk for-linus mainline

this does:

- find out the commit-id points at "for-linus"
- send a REST request to https://foo.kerkel.org/lmk:

  {
    "tree": "mainline",
    "commit": "123abc...abc555",
    "notify": "(output of $(git config user.email)"
  }

We already run a bunch of periodic jobs on repo updates and can run an 
additional check-and-fire-an-email automation job.

Would that be a useful alternative? If yes, what would be your preferred 
workflow for such tool instead of "git lmk [commit] [tree-moniker]"?

-K

Download attachment "signature.asc" of type "application/pgp-signature" (229 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ