Hi Stephen, On Mon, May 5, 2014 at 11:57 AM, Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx> wrote: > Hi Michael, > > On Mon, 5 May 2014 10:42:23 +0200 Michael Kerrisk <mtk.manpages@xxxxxxxxx> wrote: >> >> I don't know what the process is for clearing cruft out of linux-next >> is, but there's at least one piece of cruft that probably should go: > > I usually depend on maintainers to clean up their trees. > >> commit d30c01a0611d54926ac860721c933edafcc91905 >> commit 8c013e265a8eca0ada9f1aaa6cd7590698dc7231 >> commit e86263c9d00efb091a5215b9e4063378828d815c > > I can't find any of these commits in linux-next or any commits by Andrey > Vagin <avagin@xxxxxxxxxx> ... Okay, must be my problem then. Sorry for the noise. Somehow, I'm not syncing my linux-next correctly then. (Is the proper way of doing this documented somewhere?) > [P.S. Please trim replies to relevant bits ...] Ah yes--sorry. Cheers, Michael -- Michael Kerrisk Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/ Linux/UNIX System Programming Training: http://man7.org/training/ -- To unsubscribe from this list: send the line "unsubscribe linux-next" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html