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] [day] [month] [year] [list]
Message-ID: <824348.1647733664@warthog.procyon.org.uk>
Date:   Sat, 19 Mar 2022 23:47:44 +0000
From:   David Howells <dhowells@...hat.com>
To:     Ilya Dryomov <idryomov@...il.com>
Cc:     dhowells@...hat.com, Jeff Layton <jlayton@...nel.org>,
        Xiubo Li <xiubli@...hat.com>,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        Ceph Development <ceph-devel@...r.kernel.org>,
        linux-cachefs@...hat.com, linux-afs@...ts.infradead.org,
        linux-nfs@...r.kernel.org, linux-cifs@...r.kernel.org,
        v9fs-developer@...ts.sourceforge.net,
        linux-fsdevel <linux-fsdevel@...r.kernel.org>,
        LKML <linux-kernel@...r.kernel.org>
Subject: Re: Coordinating netfslib pull request with the ceph pull request

Ilya Dryomov <idryomov@...il.com> wrote:

> Given how your branch is structured, it sounds like the easiest would
> be for you to send the netfslib pull request after I send the ceph pull
> request.  Or do you have some tighter coordination in mind?

I think that's sufficient - or if I sent mine first, I can put in a big note
at the top saying it depends on yours, when you decide to post it.

David

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ