From: Valdis.Kletnieks@vt.edu
To: Susanne Oberhauser <froh@novell.com>
Cc: Jan Blunck <jblunck@suse.de>,
Linux-Kernel Mailinglist <linux-kernel@vger.kernel.org>,
opensuse-kernel@opensuse.org, opensuse@opensuse.org
Subject: Re: Testing the Current Upstream Kernel
Date: Thu, 16 Aug 2007 10:04:21 -0400 [thread overview]
Message-ID: <6891.1187273061@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Thu, 16 Aug 2007 12:28:34 +0200." <s2iwsvvlqnh.fsf@byron.suse.de>
[-- Attachment #1: Type: text/plain, Size: 1181 bytes --]
On Thu, 16 Aug 2007 12:28:34 +0200, Susanne Oberhauser said:
> Jan Blunck <jblunck@suse.de> writes:
>
> > With our openSUSE Build Service we build a daily kernel, where we take
> > nightly snapshots of the current upstream development kernel (Linus' kernel
> > tree linux-2.6.git) without any patches (besides those we need for building a
> > RPM). We do call this the vanilla kernel. It can be downloaded from:
> >
> > http://download.opensuse.org/repositories/Kernel:/Vanilla/SUSE_Factory/
>
> Would it make sense to build it for the other distros as well? like
> debian, fedora and mandrake? I mena in _theory_ we could build it for
> those distros in the build server, couldn't we?
Most of the distros prefer a chance to add their own "Special Sauce" to it
before building, and building inside their build environment (for instance,
Fedora RPM's get PGP-signed - *that* would be a trust issue right there).
The current Fedora Rawhide kernel is 'kernel-2.6.23-0.105.rc3.fc8', and a few
RPMs ago it was based against -rc2-git5, so they track *very* close. I think
that crew is managing well enough without help from the kernel.org build
server.
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
next prev parent reply other threads:[~2007-08-16 14:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <s2ihcn1vwob.fsf@totally-fudged-out-message-id>
2007-08-16 10:28 ` Susanne Oberhauser
2007-08-16 14:04 ` Valdis.Kletnieks [this message]
2007-08-17 14:31 ` Dave Jones
2007-08-17 15:49 ` Dave Jones
2007-08-15 11:08 Jan Blunck
2007-08-15 11:14 ` Sam Ravnborg
2007-08-15 11:37 ` Jan Blunck
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=6891.1187273061@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=froh@novell.com \
--cc=jblunck@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=opensuse-kernel@opensuse.org \
--cc=opensuse@opensuse.org \
/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
all inboxes | Powered by JetHome®