From: Thomas Meyer <thomas@m3y3r.de>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for May 19
Date: Mon, 19 May 2008 20:42:00 +0200 [thread overview]
Message-ID: <1211222520.30161.3.camel@dhcppc1> (raw)
In-Reply-To: <20080519174120.2083ea57.sfr@canb.auug.org.au>
Am Montag, den 19.05.2008, 17:41 +1000 schrieb Stephen Rothwell:
> News:
> I will stop making full tar balls tomorrow unless someone screams.
> The LATEST file now contains the name of the version that the
> patches are based on i.e. today, LATEST-IS-next-20080519 contains "v2.6.26-rc3".
>
> Changes since next-20080516:
>
> New tree: bkl-removal (this is Jonathan Corbet's tree)
>
> Removed trees: x86-fixes, sched-fixes (I don't know where they are
> currently).
>
> Changed trees: x86 and sched are now the new auto merged trees.
>
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
greetz
--
To unsubscribe from this list: send the line "unsubscribe linux-next" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Thomas Meyer <thomas@m3y3r.de>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for May 19
Date: Mon, 19 May 2008 20:42:00 +0200 [thread overview]
Message-ID: <1211222520.30161.3.camel@dhcppc1> (raw)
In-Reply-To: <20080519174120.2083ea57.sfr@canb.auug.org.au>
Am Montag, den 19.05.2008, 17:41 +1000 schrieb Stephen Rothwell:
> News:
> I will stop making full tar balls tomorrow unless someone screams.
> The LATEST file now contains the name of the version that the
> patches are based on i.e. today, LATEST-IS-next-20080519 contains "v2.6.26-rc3".
>
> Changes since next-20080516:
>
> New tree: bkl-removal (this is Jonathan Corbet's tree)
>
> Removed trees: x86-fixes, sched-fixes (I don't know where they are
> currently).
>
> Changed trees: x86 and sched are now the new auto merged trees.
>
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
greetz
next prev parent reply other threads:[~2008-05-19 18:42 UTC|newest]
Thread overview: 24+ 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-20 6:40 ` Herbert Xu
2008-05-19 18:42 ` Thomas Meyer [this message]
2008-05-19 18:42 ` linux-next: Tree for May 19 Thomas Meyer
2008-05-20 4:19 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
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
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=1211222520.30161.3.camel@dhcppc1 \
--to=thomas@m3y3r.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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.