public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tim Fairchild <tim@bcs4me.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: K3b and 2.6.9?
Date: Wed, 1 Sep 2004 18:37:33 +1000	[thread overview]
Message-ID: <200409011837.33073.tim@bcs4me.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0408310959340.2295@ppc970.osdl.org>

On Wednesday 01 Sep 2004 03:05,  Linus Torvalds wrote:

> But exactly _because_ it makes so much sense to just change K3b to use
> O_RDWR in its open, I'm hoping that the K3b developers won't complain too
> much about the kernel changing to require more strict checking (obviously,
> I can understand that _users_ will complain - they only see the "it
> stopped working" part).

Thanks for the info. Yes, this is what I am seeing a lot on linux user 
lists... "Don't use kernel 2.6.8.1 - it is broken" and so forth. Which is why 
I was looking to gain some insight into the k3b problem so I feel I know a 
little about the subject when on the lists... And also like to do testing 
when I can to help... what little help it might be.

thanks,

tim

  reply	other threads:[~2004-09-01  8:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-30  0:47 K3b and 2.6.9? Tim Fairchild
2004-08-30 13:07 ` Alan Cox
2004-08-31  1:51   ` Tim Fairchild
2004-08-31  2:29     ` Linus Torvalds
2004-08-31  6:26       ` Frank Steiner
2004-08-31 16:29         ` Linus Torvalds
2004-08-31 10:37       ` Tim Fairchild
2004-08-31 17:05         ` Linus Torvalds
2004-09-01  8:37           ` Tim Fairchild [this message]
2004-08-31 20:16       ` ismail dönmez
2004-08-31 20:33         ` Linus Torvalds
2004-08-31 22:01           ` Tim Fairchild
2004-09-01  8:27           ` Tim Fairchild

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=200409011837.33073.tim@bcs4me.com \
    --to=tim@bcs4me.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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