From: Stephen Rothwell <sfr@canb.auug.org.au>
To: linux-next@vger.kernel.org
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: linux-next: cleanup time
Date: Mon, 14 Nov 2011 00:52:52 +1100 [thread overview]
Message-ID: <20111114005252.ed41504cabda72e4e8b60eac@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 553 bytes --]
Hi all,
Since we are out of the merge window, could people with trees in
linux-next please take th opportunity to clean them up. Hopefully,
Linus took all the contents of your trees, in which case git
trees/branches should be reset to be a (subset of) Linus' tree (this will
be a noop for those for whom Linus pulled that actual branch that is in
linux-next). For quilt series, you should remove any patches that Linus
has merged.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
reply other threads:[~2011-11-13 13:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20111114005252.ed41504cabda72e4e8b60eac@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
/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