public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Paul Moore <paul@paul-moore•com>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org
Subject: linux-next: the selinux tree needs cleaning up
Date: Wed, 18 Jun 2014 08:40:46 +1000	[thread overview]
Message-ID: <20140618084046.1bce12cc@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 462 bytes --]

Hi Paul,

The selinux tree (git://git.infradead.org/users/pcmoore/selinux#next)
contains some commits going back to January and also has merges of
v3.13, v3.14 and v3.15 in it.  If you rebase that tree onto v3.16-rc1,
you find that it has onlt 2 unique commits (the most recent 2) which
means that the others were merged upstream after being rewritten.  :-(

Please clean this up.
-- 
Cheers,
Stephen Rothwell                    sfr@canb•auug.org.au

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

             reply	other threads:[~2014-06-17 22:40 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-17 22:40 Stephen Rothwell [this message]
2014-06-18 18:26 ` linux-next: the selinux tree needs cleaning up Paul Moore
2014-06-19 15:08   ` Stephen Rothwell
2014-06-19 19:47     ` Paul Moore
2014-06-19 22:59       ` Stephen Rothwell
2014-06-20  3:43         ` Serge E. Hallyn
2014-06-20  3:59           ` Stephen Rothwell
2014-06-20 14:57             ` Serge E. Hallyn
2014-06-20 16:06         ` Paul Moore
2014-06-24 18:03           ` Paul Moore
2014-06-24 23:59             ` Stephen Rothwell
2014-06-25 10:51               ` James Morris
2014-06-25 22:12                 ` Stephen Rothwell
2014-06-27  2:41                   ` James Morris
2014-06-25 14:14               ` Paul Moore

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=20140618084046.1bce12cc@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=paul@paul-moore$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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