From: Nico -telmich- Schottelius <nico-linux-next@schottelius.org>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>, linux-next@vger.kernel.org
Subject: Re: linux-next test scripts
Date: Fri, 13 Mar 2009 09:03:48 +0100 [thread overview]
Message-ID: <20090313080348.GC3246@denkbrett.schottelius.org> (raw)
In-Reply-To: <20090212202036.GA31203@pengutronix.de>
[-- Attachment #1: Type: text/plain, Size: 1065 bytes --]
Uwe Kleine-König [Thu, Feb 12, 2009 at 09:20:37PM +0100]:
> Hello,
>
> On Fri, Feb 06, 2009 at 03:20:22PM +0100, Uwe Kleine-König wrote:
> > I plan to setup something similar to linux-next for the Pengutronix test
> > lab to build a tree that contains the work of all our developers for
> > daily testing.
> >
> > It would be really great if I could take a look into your scripts to
> > manage linux-next. I tried searching the web for them, but without
> > success.
> >
> > Are the scripts somewhere available without being found by me? If yes,
> > where are they, if not, do you can publish them somewhere?
> After some more search I found the script by James Bottomley[1].
I'm also maintaining some smaller scripts for maintaining all the
kernel testing / building / installation stuff:
http://git.schottelius.org/?p=nsbin;a=tree;f=linux;hb=HEAD
Nico
--
Think about Free and Open Source Software (FOSS).
http://nico.schottelius.org/documentations/foss/the-term-foss/
PGP: BFE4 C736 ABE5 406F 8F42 F7CF B8BE F92A 9885 188C
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-03-13 8:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-06 14:20 linux-next test scripts Uwe Kleine-König
2009-02-12 20:20 ` Uwe Kleine-König
2009-03-13 8:03 ` Nico -telmich- Schottelius [this message]
2009-03-13 8:37 ` Uwe Kleine-König
2009-03-13 9:46 ` Nico -telmich- Schottelius
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=20090313080348.GC3246@denkbrett.schottelius.org \
--to=nico-linux-next@schottelius.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=u.kleine-koenig@pengutronix.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).