From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Thomas Meyer <thomas@m3y3r.de>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for May 19
Date: Tue, 20 May 2008 14:19:01 +1000 [thread overview]
Message-ID: <20080520141901.6395a2a1.sfr@canb.auug.org.au> (raw)
In-Reply-To: <1211222520.30161.3.camel@dhcppc1>
[-- Attachment #1: Type: text/plain, Size: 496 bytes --]
Hi Thomas,
On Mon, 19 May 2008 20:42:00 +0200 Thomas Meyer <thomas@m3y3r.de> wrote:
>
> Is it intentional that kernel.release is:
>
> $ cat include/config/kernel.release
> 2.6.26-rc3-next-20080519-sched-devel.git
>
> all predecessors have had names like:
> 2.6.26-rc2-next-20080516
It was not intentional, I missed it sneaking in. It seems to be gone
again today.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2008-05-20 4:19 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-19 7:41 linux-next: Tree for May 19 Stephen Rothwell
2008-05-19 10:27 ` [BUG] linux-next: Tree for May 19 - BUG at arch/x86/kernel/io_apic_64.c:353! Kamalesh Babulal
2008-05-21 17:26 ` [BUG] linux-next: Tree for May 19/20/21 " Kamalesh Babulal
2008-05-22 0:15 ` Stephen Rothwell
2008-05-22 10:22 ` Kamalesh Babulal
2008-05-19 17:08 ` [BUILD_FAILURE] linux-next: Tree for May 19 - build fails on cryptd_alloc_hash () Kamalesh Babulal
2008-05-19 17:26 ` Randy Dunlap
2008-05-20 6:40 ` Herbert Xu
2008-05-19 18:42 ` linux-next: Tree for May 19 Thomas Meyer
2008-05-20 4:19 ` Stephen Rothwell [this message]
2009-05-19 8:30 Stephen Rothwell
2010-05-19 6:35 Stephen Rothwell
2011-05-19 3:59 Stephen Rothwell
2014-05-19 8:39 Stephen Rothwell
2015-05-19 7:30 Stephen Rothwell
2016-05-19 6:45 Stephen Rothwell
2017-05-19 5:03 Stephen Rothwell
2020-05-19 18:03 Stephen Rothwell
2021-05-19 5:32 Stephen Rothwell
2022-05-19 9:49 Stephen Rothwell
2023-05-19 3:07 Stephen Rothwell
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=20080520141901.6395a2a1.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=thomas@m3y3r.de \
/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).