From: Matthias Andree <matthias.andree@gmx.de>
To: Greg KH <greg@kroah.com>
Cc: Matthew Wilcox <matthew@wil.cx>,
Douglas Gilbert <dougg@torque.net>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: lsscsi-0.17 released
Date: Wed, 22 Feb 2006 21:22:19 +0100 [thread overview]
Message-ID: <20060222202219.GA25121@merlin.emma.line.org> (raw)
In-Reply-To: <20060222183226.GA12542@kroah.com>
On Wed, 22 Feb 2006, Greg KH wrote:
> On Wed, Feb 22, 2006 at 07:00:15PM +0100, Matthias Andree wrote:
> > OK, just post an announcement to l-k when sysfs has stabilized enough to
> > be worth bothering.
>
> Um, this was a "bugfix".
Granted.
> The kernel was creating multiple symlinks with
> the same name, in the same directory, pointing to different locations.
> How do you expect us to fix that in a format that does not change the
> name of the symlink?
>
> People sure are grumpy this morning...
If you say so. I'd call it pure pragmatism: if the sysfs interface
still changes every other week or so, it's just annoying to chase these
changes in applications, so it seems just practical to wait until all
the bug fixes that require interface changes are in and the rate of
incompatible changes is well below 2/year -- and all the interesting
stuff is there.
--
Matthias Andree
next prev parent reply other threads:[~2006-02-22 20:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-21 23:39 lsscsi-0.17 released Douglas Gilbert
2006-02-22 8:50 ` Matthias Andree
2006-02-22 15:01 ` Douglas Gilbert
2006-02-22 16:06 ` Matthias Andree
2006-02-22 16:27 ` Douglas Gilbert
2006-02-22 16:34 ` Matthew Wilcox
2006-02-22 16:38 ` Randy.Dunlap
2006-02-22 17:14 ` Greg KH
2006-02-22 18:00 ` Matthias Andree
2006-02-22 18:32 ` Greg KH
2006-02-22 20:22 ` Matthias Andree [this message]
2006-02-22 17:59 Douglas Gilbert
2006-02-22 18:37 ` Greg KH
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=20060222202219.GA25121@merlin.emma.line.org \
--to=matthias.andree@gmx.de \
--cc=dougg@torque.net \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=matthew@wil.cx \
/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).