From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Michael Kerrisk <mtk.manpages@gmail.com>
Cc: linux-next@vger.kernel.org,
Linux Kernel <linux-kernel@vger.kernel.org>,
Andrey Vagin <avagin@openvz.org>
Subject: Re: linux-next: Tree for May 5
Date: Mon, 5 May 2014 19:57:11 +1000 [thread overview]
Message-ID: <20140505195711.fcce1825483f7a1ce707c2c6@canb.auug.org.au> (raw)
In-Reply-To: <CAHO5Pa0D8bxBV98feBt2qk_gb3XdTDcmaa6bD7eQv4UOdjcFrA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 691 bytes --]
Hi Michael,
On Mon, 5 May 2014 10:42:23 +0200 Michael Kerrisk <mtk.manpages@gmail.com> 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@openvz.org> ...
[P.S. Please trim replies to relevant bits ...]
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-05-05 9:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-05 7:14 linux-next: Tree for May 5 Stephen Rothwell
2014-05-05 8:42 ` Michael Kerrisk
2014-05-05 9:57 ` Stephen Rothwell [this message]
2014-05-05 10:06 ` Michael Kerrisk (man-pages)
2014-05-05 10:26 ` Stephen Rothwell
2014-05-05 10:45 ` Michael Kerrisk (man-pages)
-- strict thread matches above, loose matches on Subject: below --
2023-05-05 14:25 Mark Brown
2022-05-05 10:29 Stephen Rothwell
2021-05-05 2:42 Stephen Rothwell
2020-05-05 7:15 Stephen Rothwell
2020-05-05 9:06 ` Anders Roxell
2017-05-05 4:22 Stephen Rothwell
2016-05-05 6:06 Stephen Rothwell
2015-05-05 4:53 Stephen Rothwell
2011-05-05 3:49 Stephen Rothwell
2011-05-07 3:24 ` Jean-Christophe PLAGNIOL-VILLARD
2011-05-09 5:54 ` Stephen Rothwell
2010-05-05 2:34 Stephen Rothwell
2009-05-05 5:34 Stephen Rothwell
2009-05-05 9:49 ` Nico -telmich- Schottelius
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140505195711.fcce1825483f7a1ce707c2c6@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=avagin@openvz.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).