From: Ian Kumlien <pomac@vapor.com>
To: Al Viro <viro@ftp.linux.org.uk>
Cc: "Wed, 9 Nov 2005 13:03:07 +0100" <grundig@teleline.es>,
marado@isp.novis.pt, Linux-kernel@vger.kernel.org,
fawadlateef@gmail.com, s0348365@sms.ed.ac.uk,
hostmaster@ed-soft.at, jerome.lacoste@gmail.com,
carlsj@yahoo.com
Subject: Re: New Linux Development Model
Date: Wed, 09 Nov 2005 17:32:19 +0100 [thread overview]
Message-ID: <1131553939.2413.94.camel@localhost> (raw)
In-Reply-To: <20051109155846.GZ7992@ftp.linux.org.uk>
[-- Attachment #1: Type: text/plain, Size: 672 bytes --]
On Wed, 2005-11-09 at 15:58 +0000, Al Viro wrote:
> On Wed, Nov 09, 2005 at 04:49:17PM +0100, Ian Kumlien wrote:
>
> > > People is allowed to have different opinions than you, deal with it.
> >
> > And that applies to me to, now deal with it.
>
> That's easy - you are welcome to maintain whatever tree you like according
> to your opinion. Same as everybody else.
ROTFLOL, Yeah i know, I just think it's more about the users need than
'stable' and 'unstable', Just label it experimental so the user knows
what they are getting into. (Just like the examples posted in other
mails)
--
Ian Kumlien <pomac () vapor ! com> -- http://pomac.netswarm.net
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2005-11-09 16:31 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-09 1:47 New Linux Development Model Ian Kumlien
2005-11-09 11:08 ` Marcos Marado
2005-11-09 11:30 ` Ian Kumlien
2005-11-09 12:03 ` Wed, 9 Nov 2005 13:03:07 +0100
2005-11-09 15:49 ` Ian Kumlien
2005-11-09 15:58 ` Al Viro
2005-11-09 16:32 ` Ian Kumlien [this message]
2005-11-09 12:37 ` Marcos Marado
2005-11-09 16:01 ` Ian Kumlien
2005-11-10 0:55 ` Alistair John Strachan
2005-11-10 15:10 ` Mark Lord
2005-11-10 19:29 ` Alistair John Strachan
2005-11-10 19:47 ` Ian Kumlien
2005-11-09 19:05 ` Bill Davidsen
2005-11-09 20:10 ` Marcos Marado
2005-11-10 0:57 ` Alistair John Strachan
2005-11-10 20:08 ` Bill Davidsen
2005-11-10 20:21 ` Alistair John Strachan
2005-11-12 13:45 ` Bill Davidsen
-- strict thread matches above, loose matches on Subject: below --
2005-11-05 9:42 hostmaster
2005-11-05 10:29 ` Francois Romieu
2005-11-05 11:29 ` Jean Delvare
2005-11-05 13:19 ` Edgar Hucek
2005-11-05 13:44 ` Adrian Bunk
2005-11-05 13:47 ` Alistair John Strachan
2005-11-05 22:23 ` Mark Lord
2005-11-06 0:28 ` Alistair John Strachan
2005-11-05 14:34 ` Jesper Juhl
2005-11-05 14:48 ` Oliver Neukum
2005-11-05 14:56 ` Fawad Lateef
2005-11-05 15:28 ` Adrian Bunk
2005-11-06 10:52 ` jerome lacoste
2005-11-06 11:55 ` Edgar Hucek
2005-11-06 12:39 ` Adrian Bunk
2005-11-06 12:57 ` Bernd Petrovitsch
2005-11-06 17:38 ` Jean Delvare
[not found] ` <436DEEFC.4020301@ed-soft.at>
2005-11-06 13:43 ` jerome lacoste
2005-11-09 0:11 ` caszonyi
2005-11-09 0:23 ` Con Kolivas
2005-11-09 7:00 ` Diego Calleja
2005-11-09 12:30 ` jerome lacoste
2005-11-09 14:03 ` caszonyi
2005-11-09 15:45 ` Marcos Marado
2005-11-06 16:50 ` John Carlson
2005-11-06 18:17 ` Bernd Petrovitsch
2005-11-09 0:16 ` caszonyi
2005-11-06 15:22 ` Jim Nance
2005-11-06 16:55 ` John Carlson
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=1131553939.2413.94.camel@localhost \
--to=pomac@vapor.com \
--cc=Linux-kernel@vger.kernel.org \
--cc=carlsj@yahoo.com \
--cc=fawadlateef@gmail.com \
--cc=grundig@teleline.es \
--cc=hostmaster@ed-soft.at \
--cc=jerome.lacoste@gmail.com \
--cc=marado@isp.novis.pt \
--cc=s0348365@sms.ed.ac.uk \
--cc=viro@ftp.linux.org.uk \
/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