From: Randy Dunlap <randy.dunlap@oracle.com>
To: linux-next@vger.kernel.org
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Richard Holden <aciddeath@gmail.com>
Subject: Re: Automated Build Infrastructure
Date: Sun, 16 Nov 2008 21:24:55 -0800 [thread overview]
Message-ID: <49210027.8070608@oracle.com> (raw)
In-Reply-To: <4920F951.5080109@oracle.com>
Randy Dunlap wrote:
> Stephen Rothwell wrote:
>> Hi Richard,
>>
>> On Sun, 16 Nov 2008 20:32:39 -0700 Richard Holden <aciddeath@gmail.com> wrote:
>>> Does anyone have any scripts to kick off compilation when Stephen
>>> releases a new linux-next? I've started to plan out my own but wanted
>>> to see if anyone had something first so I don't reinvent the wheel.
>> In case it helps, your most reliable trigger would be the LATEST-IS file
>> in http://www.kernel.org/pub/linux/kernel/people/sfr/linux-next/
>> changing. I think Randy Dunlap (cc'd) has some stuff.
>
> Hi,
>
> My scripts are available in
> http://www.xenotime.net/linux/scripts/
>
> The scripts are: grab_kernel (for mainline), grab_next (for -next),
> and get-mmotm (for mmotm). They all work with tarballs and patches,
> not git trees. get-mmotm requires an mainline tree for its patch
> series to be applied to. The 'kcurrent' script tells me what
> linux-next or mmotm applies to:
>
> The latest stable version of the Linux kernel is: 2.6.27.6
> The latest prepatch for the stable Linux kernel tree is: 2.6.28-rc5
> The latest snapshot for the stable Linux kernel tree is: 2.6.28-rc5-git1
> The latest 2.4 version of the Linux kernel is: 2.4.36.9
> The latest prepatch for the 2.4 Linux kernel tree is: 2.4.37-rc2
> The latest 2.2 version of the Linux kernel is: 2.2.26
> The latest prepatch for the 2.2 Linux kernel tree is: 2.2.27-rc2
> The latest -mm patch to the stable Linux kernels is: 2.6.28-rc2-mm1
> mmotm-2008-1114-2050 ... applies to: 2.6.28-rc4
> next-20081114 ... applies to: v2.6.28-rc4
>
> grab_kernel downloads & applies any mainline kernel (except for
> -stable kernels); it knows how to apply -rc & -git patches (zipped).
>
> If you have any questions about them, just ask.
OK, these scripts don't do the automated kickoff part.
For that, I'm using Crucible (crucible.sf.net).
The scripts are all in the subversion repository at sf.net.
--
~Randy
next prev parent reply other threads:[~2008-11-17 5:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-17 3:32 Automated Build Infrastructure Richard Holden
2008-11-17 3:45 ` Stephen Rothwell
2008-11-17 4:55 ` Randy Dunlap
2008-11-17 5:24 ` Randy Dunlap [this message]
2008-11-26 19:59 ` Randy Dunlap
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=49210027.8070608@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=aciddeath@gmail.com \
--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 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).