From: Jeff Mahoney <jeffm@suse.com>
To: doiggl@velocitynet.com.au, reiserfs-devel@vger.kernel.org
Subject: Re: Is the patchset[patch 00/29] reiserfs cleanup patchset in openSUSE Build Service > Projects > Kernel:linux-next > kernel-vanilla ?
Date: Fri, 27 Jun 2014 09:03:38 -0400 [thread overview]
Message-ID: <53AD6BAA.5010204@suse.com> (raw)
In-Reply-To: <0d2c3b96860564343a97c458cdf46c27@mail.velocitynet.com.au>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 6/26/14, 9:09 PM, doiggl@velocitynet.com.au wrote:
> Hello, Is the patchset[patch 00/29] reiserfs cleanup patchset in
> openSUSE Build Service > Projects > Kernel:linux-next >
> kernel-vanilla ? Thanks Glenn
>
> https://build.opensuse.org/package/show/Kernel:linux-next/kernel-vanilla
>
>
[linux-3.16-rc2-next-20140625.tar.bz2 ]
>
Yes. It was included in the upstream kernel in 3.16-rc1.
- -Jeff
- --
Jeff Mahoney
SUSE Labs
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.19 (Darwin)
iQIcBAEBAgAGBQJTrWuqAAoJEB57S2MheeWyeTEQAKoCgRPQN4l4J9jNfXGXHOxl
wRJpi2Dab0RwFw9xSQghwZMhrpf5Zi//VW7ro0MKGOeU09lhX67TxPg+WLX1M9i1
3CkLZx5jRdei3e8P5Y+PxV3AtZ3oS62NnRT5gL0kCRwPqv5oLtnC+pllhCiDqwrA
apIgLdebrnxnjg1hPdmLqSjuNYsht9POtGjfJRu6oBI6iSuQqWWrqjP1Go5vsUsL
X1+xn6V0qOhqV0MzOBZ/+vwo94v82WqfrIvLVfP9IZAQTpA8zZpqH2dyBjgSZLu0
POR/g9Z5UDMLLbZthkw3HSzxFtON3n6NPBTIA2ah35cE2xBg5k2HPy7UqAeG9Wzn
/JzNq08XQgMNON4OENBgJ89AJTszCfho8XHZdgxDFWGl2lI/JXxM2cNFUoAwy37C
gLeBNdPvXqZnNUMvyzTOKfBMudmgsI5AE4ws1GYXNR+DI/fdzLrsP4hbBirCDFxu
ppb1GVguwszkdG0Z5f4pO9hubx9NQvyG9AsOmUDM/+0RBiSrcrnV60MhcREXEeB+
9S3X0/0kY4LZXN5Ubw2IL+lpS6M23MDFVI0ACztQWot2hJDuCQGMOxxVdlzFfYJ8
tu+iPg6c6ibSMtqGVcLpdneLk2U3Vx9zOK06dN0aAMAL0h4oIGwqT4VsGGkLR1Ur
mvxV2j8LLHxvfjloBK1R
=Gn4K
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2014-06-27 13:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-27 1:09 Is the patchset[patch 00/29] reiserfs cleanup patchset in openSUSE Build Service > Projects > Kernel:linux-next > kernel-vanilla ? doiggl
2014-06-27 13:03 ` Jeff Mahoney [this message]
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=53AD6BAA.5010204@suse.com \
--to=jeffm@suse.com \
--cc=doiggl@velocitynet.com.au \
--cc=reiserfs-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.