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 10:46:50 +0100 [thread overview]
Message-ID: <20090313094650.GA30900@denkbrett.schottelius.org> (raw)
In-Reply-To: <20090313083701.GB15754@pengutronix.de>
[-- Attachment #1: Type: text/plain, Size: 1175 bytes --]
Uwe Kleine-König [Fri, Mar 13, 2009 at 09:37:01AM +0100]:
> > > > 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
> Thanks, but I think it doesn't include what I'm looking for. You only
> seem to build bleeding edge (in next-build.sh) but you don't merge
> different trees before.
Well, that is something to be written, but also just a loop similar to
> BTW, I don't see the reason for linux/fetch-branches.sh, why not rely on
> git remote udpate?
that one here. I think I wrote it that way, to use the loop for merging
later.
But you are totally right: git remote update is the much simpler way here.
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 --]
prev parent reply other threads:[~2009-03-13 9:46 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
2009-03-13 8:37 ` Uwe Kleine-König
2009-03-13 9:46 ` Nico -telmich- Schottelius [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=20090313094650.GA30900@denkbrett.schottelius.org \
--to=nico-linux-next@schottelius$(echo .)org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=u.kleine-koenig@pengutronix$(echo .)de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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