public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Blunck <jblunck@suse.de>
To: linux-kernel@vger.kernel.org
Subject: Re: Testing the Current Upstream Kernel
Date: Wed, 15 Aug 2007 11:37:10 +0000 (UTC)	[thread overview]
Message-ID: <f9uoh6$q2i$1@sea.gmane.org> (raw)
In-Reply-To: 20070815111404.GA2783@uranus.ravnborg.org

On Wed, 15 Aug 2007 13:14:04 +0200, Sam Ravnborg wrote:

> On Wed, Aug 15, 2007 at 01:08:51PM +0200, Jan Blunck wrote:
>> (besides those we need for building a RPM).
> 
> Are these openSUSE specific or something we ought to apply to mainline?
> 

If there are patches (at the moment there are none) than they are 
openSUSE Build Service specific. Otherwise we usually send patches 
upstream.

Regards,
	Jan

-- 
Jan Blunck <jblunck@suse.de>


  reply	other threads:[~2007-08-15 11:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-15 11:08 Testing the Current Upstream Kernel Jan Blunck
2007-08-15 11:14 ` Sam Ravnborg
2007-08-15 11:37   ` Jan Blunck [this message]
     [not found] <s2ihcn1vwob.fsf@totally-fudged-out-message-id>
2007-08-16 10:28 ` Susanne Oberhauser
2007-08-16 14:04   ` Valdis.Kletnieks
2007-08-17 14:31     ` Dave Jones
2007-08-17 15:49       ` Dave Jones

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='f9uoh6$q2i$1@sea.gmane.org' \
    --to=jblunck@suse.de \
    --cc=linux-kernel@vger.kernel.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