From: Michael Buesch <mb@bu3sch.de>
To: Adrian Bunk <bunk@stusta.de>
Cc: Chuck Ebbert <76306.1226@compuserve.com>,
Paul Fulghum <paulkf@microgate.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.16.28
Date: Sat, 26 Aug 2006 18:35:10 +0200 [thread overview]
Message-ID: <200608261835.11177.mb@bu3sch.de> (raw)
In-Reply-To: <20060826155159.GJ4765@stusta.de>
On Saturday 26 August 2006 17:51, Adrian Bunk wrote:
> On Sat, Aug 26, 2006 at 10:20:43AM -0400, Chuck Ebbert wrote:
> > In-Reply-To: <20060826003639.GA4765@stusta.de>
> >
> > On Sat, 26 Aug 2006 02:36:39 +0200, Adrian Bunk wrote:
> >
> > > Location:
> > > ftp://ftp.kernel.org/pub/linux/kernel/v2.6/
> >
> > Could you post the incremental patch as a reply like Greg does?
>
> After Michaels reminder I've put it at ftp.kernel.org .
Well, actually it would be good to have that incremental patch
as a reply to the mail (like Greg does).
The reason I asked for the incremental patch is that I have to search
the diff and decide if I have to apply that to my server kernel or not.
If it was as reply, this would be much easier.
But anyway. Thanks for maintaining 2.6.16.x. I very much like
to have a stable series kernel for my server.
--
Greetings Michael.
next prev parent reply other threads:[~2006-08-26 16:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-26 14:20 Linux 2.6.16.28 Chuck Ebbert
2006-08-26 15:51 ` Adrian Bunk
2006-08-26 16:35 ` Michael Buesch [this message]
2006-08-26 18:30 ` Paul Fulghum
2006-08-27 1:37 ` Adrian Bunk
-- strict thread matches above, loose matches on Subject: below --
2006-08-26 0:36 Adrian Bunk
2006-08-26 11:00 ` Michael Buesch
2006-08-26 12:55 ` Adrian Bunk
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=200608261835.11177.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=76306.1226@compuserve.com \
--cc=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.org \
--cc=paulkf@microgate.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.