From: Bill Davidsen <davidsen@tmr.com>
To: Ben Collins <bcollins@debian.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: IEEE-1394 problem on init [ was Re: Linux 2.4.21-rc1 ]
Date: Sat, 26 Apr 2003 06:36:13 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.3.96.1030426063455.20200B-100000@gatekeeper.tmr.com> (raw)
In-Reply-To: <20030425181610.GA2774@phunnypharm.org>
On Fri, 25 Apr 2003, Ben Collins wrote:
> > Yes, and I miss why that matters. Let me see if I can make the idea clear
> > to you:
> > 2.4.22-pre5 some code
> > 2.4.22-pre5-bk1 fixes
> > 2.4.22-pre5-bk2 more fixes
> > 2.4.22-pre5-bk3 still more fixes
> > 2.4.22-pre6 fixes to date plus major changes
> >
> > So when a maintainer got something major it wouldn't go into bk (the
> > commercial software database) until a new -pre, while the -bk patches
> > available for download would get the fixes only.
>
> What if a fix depends on a major-change-patch? What if a fix is itself a
> major change?
Time for a -pre. That's a change management decision. Hopefully -pre would
be somewhat closer spaced than has happened with 2.4.21.
--
bill davidsen <davidsen@tmr.com>
CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.
next prev parent reply other threads:[~2003-04-26 10:29 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-23 12:29 IEEE-1394 problem on init [ was Re: Linux 2.4.21-rc1 ] Tony Spinillo
2003-04-23 12:53 ` Stelian Pop
2003-04-23 13:01 ` Ben Collins
2003-04-23 13:22 ` Stelian Pop
2003-04-23 13:32 ` Ben Collins
2003-04-23 13:46 ` Ben Collins
2003-04-23 13:58 ` Stelian Pop
2003-04-23 13:54 ` Ben Collins
2003-04-23 14:21 ` Stelian Pop
2003-04-23 14:23 ` Ben Collins
2003-04-23 14:51 ` Stelian Pop
2003-04-23 14:44 ` Ben Collins
2003-04-23 14:48 ` Ben Collins
2003-04-23 15:29 ` Stelian Pop
2003-04-23 19:13 ` Marcelo Tosatti
2003-04-23 19:05 ` Ben Collins
2003-04-23 19:27 ` Marcelo Tosatti
2003-04-23 20:20 ` Stelian Pop
2003-04-23 20:24 ` Ben Collins
2003-04-23 20:42 ` Stelian Pop
2003-04-26 8:29 ` The IEEE-1394 saga continued... [ was: IEEE-1394 problem on init ] Stelian Pop
2003-04-26 14:34 ` Ben Collins
2003-04-26 16:10 ` Stelian Pop
2003-04-26 16:12 ` Ben Collins
2003-04-26 17:00 ` Stelian Pop
2003-04-26 16:59 ` Ben Collins
2003-04-26 14:40 ` Ben Collins
2003-04-26 16:23 ` Stelian Pop
2003-04-26 16:25 ` Ben Collins
2003-04-26 17:15 ` Stelian Pop
2003-04-24 21:44 ` IEEE-1394 problem on init [ was Re: Linux 2.4.21-rc1 ] Bill Davidsen
2003-04-24 21:41 ` Ben Collins
2003-04-25 18:06 ` Bill Davidsen
2003-04-25 18:16 ` Ben Collins
2003-04-26 10:36 ` Bill Davidsen [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-04-21 18:47 Linux 2.4.21-rc1 Marcelo Tosatti
2003-04-23 7:59 ` IEEE-1394 problem on init [ was Re: Linux 2.4.21-rc1 ] Stelian Pop
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=Pine.LNX.3.96.1030426063455.20200B-100000@gatekeeper.tmr.com \
--to=davidsen@tmr.com \
--cc=bcollins@debian.org \
--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;
as well as URLs for NNTP newsgroup(s).