On Sun, 20 Jul 2014 19:34:34 +0200 David Herrmann <dh.herrmann@xxxxxxxxx> wrote: > This is v4 of the File-Sealing and memfd_create() patches. You can find v1 with > a longer introduction at gmane [1], there's also v2 [2] and v3 [3] available. > See also the article about sealing on LWN [4], and a high-level introduction on > the new API in my blog [5]. Last but not least, man-page proposals are > available in my private repository [6]. > > ... > > > [1] memfd v1: http://thread.gmane.org/gmane.comp.video.dri.devel/102241 > [2] memfd v2: http://thread.gmane.org/gmane.linux.kernel.mm/115713 > [3] memfd v3: http://thread.gmane.org/gmane.linux.kernel.mm/118721 > [4] LWN article: https://lwn.net/Articles/593918/ > [5] API Intro: http://dvdhrm.wordpress.com/2014/06/10/memfd_create2/ > [6] Man-pages: http://cgit.freedesktop.org/~dvdhrm/man-pages/log/?h=memfd > [7] Dev-repo: http://cgit.freedesktop.org/~dvdhrm/linux/log/?h=memfd This is unconventional and a little irritating. I'm OK with running around chasing down web pages but we generally don't do that in changelogs. I'm not sure why really, maybe partly because things bitrot, partly because that's where people expect to find things, partly because people like work down caves and on airplanes ;) Another downside is that if a reviewer wants to comment on some piece of text, it isn't available for the usual reply-to-all quoting. So... Could you please put together a plain old text/plain changelog which actually describes this patchset and send it along? Everything which people need/want to know, all in one place? That text should be maintained alongside the patches themselves, should there be future versions. Now excuse me, I have a bunch of web pages to go and read ;) <reads "[1] memfd v1"> OK, I immediately have questions and I see significant review feedback, so either that document is out of date or that review feedback was ignored. Help. Where do I (and all future readers of these patches) go to get an up to date and complete description of this patchset?? -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
