All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Collins <bcollins@debian.org>
To: Mike Fedyk <mfedyk@matchmail.com>
Cc: Bradley Chapman <kakadu_croc@yahoo.com>,
	Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org,
	linux1394-devel@lists.sourceforge.net
Subject: Re: This bug appears under 2.6.0-test8 as well (was: 2.6.0-test7-mm1)
Date: Mon, 27 Oct 2003 15:21:31 -0500	[thread overview]
Message-ID: <20031027202131.GW7904@phunnypharm.org> (raw)
In-Reply-To: <20031027201348.GH4511@matchmail.com>

On Mon, Oct 27, 2003 at 12:13:48PM -0800, Mike Fedyk wrote:
> On Sat, Oct 18, 2003 at 03:46:17PM -0400, Ben Collins wrote:
> > As would be expected considering I'm holding off changes to let 2.6
> > focus on core issues. The "bug" is pretty much harmless as-is, even if
> > noisy, and wont show up under normal compiles with debugging disables.
> > 
> > Plus, my fix is a little more than trivial, so I'm keeping it for 2.6.1.
> 
> Oh great, let's wait for the "little more than trivial" bug fixes until
> after it's released....
> 
> I understand that you're busy, and your schedule may force you to wait until
> after 2.6.0, but 2.6-test is to help get the bugs out of a release, and this
> is a bug fix so it should be accepted...


Obviously you haven't been reading Linus' posts about what he'll accept
into 2.6.0-test before 2.6.0 is final. He wont take my patches, and
rightfully so.

This isn't a matter of my choice, it's a matter of timing. Get over it,
and download the latest stuff from linux1394.org if you need it that
badly. Here's a hint:

# cd /usr/src/linux-2.6.0-test9
# rm -rf drivers/ieee1394
# wget -o trunk.tar.gz http://www.linux1394.org/viewcvs/trunk/trunk.tar.gz?tarball=1
# tar zxf trunk.tar.gz 
# mv trunk drivers/ieee1394
# rm -f trunk.tar.gz

It doesn't get any simpler than that.

-- 
Debian     - http://www.debian.org/
Linux 1394 - http://www.linux1394.org/
Subversion - http://subversion.tigris.org/
WatchGuard - http://www.watchguard.com/

  reply	other threads:[~2003-10-27 20:36 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-15 10:11 2.6.0-test7-mm1 Bradley Chapman
2003-10-15 10:22 ` 2.6.0-test7-mm1 Andrew Morton
2003-10-15 12:34   ` 2.6.0-test7-mm1 Bradley Chapman
2003-10-15 12:46     ` 2.6.0-test7-mm1 Tim Schmielau
2003-10-15 12:53       ` 2.6.0-test7-mm1 Bradley Chapman
2003-10-15 17:28     ` 2.6.0-test7-mm1 Andrew Morton
2003-10-15 17:40       ` 2.6.0-test7-mm1 Ben Collins
2003-10-15 17:53         ` 2.6.0-test7-mm1 Andrew Morton
2003-10-16  2:25           ` 2.6.0-test7-mm1 Ben Collins
2003-10-16 14:04             ` 2.6.0-test7-mm1 Anton Blanchard
2003-10-18 12:39             ` 2.6.0-test7-mm1 Kristian Høgsberg
2003-10-18 13:27               ` 2.6.0-test7-mm1 Ben Collins
2003-10-18 18:07                 ` This bug appears under 2.6.0-test8 as well (was: 2.6.0-test7-mm1) Bradley Chapman
2003-10-18 19:46                   ` Ben Collins
2003-10-27 20:13                     ` Mike Fedyk
2003-10-27 20:21                       ` Ben Collins [this message]
2003-10-15 21:14   ` 2.6.0-test7-mm1 Alexander Hoogerhuis
2003-10-15 21:44     ` 2.6.0-test7-mm1 Andrew Morton

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=20031027202131.GW7904@phunnypharm.org \
    --to=bcollins@debian.org \
    --cc=akpm@osdl.org \
    --cc=kakadu_croc@yahoo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux1394-devel@lists.sourceforge.net \
    --cc=mfedyk@matchmail.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.