mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Kay Sievers <kay.sievers@vrfy.org>
Cc: Pavel Machek <pavel@ucw.cz>, Dave Jones <davej@redhat.com>,
	Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH -mm] swsusp: userland interface (rev 2)
Date: Fri, 27 Jan 2006 12:24:12 +0100	[thread overview]
Message-ID: <200601271224.12983.rjw@sisk.pl> (raw)
In-Reply-To: <20060127034248.GA27861@vrfy.org>

Hi,

On Friday, 27 January 2006 04:42, Kay Sievers wrote:
> On Wed, Jan 25, 2006 at 09:09:27PM -0500, Jim Crilly wrote:
> > On 01/24/06 11:44:37PM +0100, Pavel Machek wrote:
> > > On Út 24-01-06 17:38:34, Dave Jones wrote:
> > > >  > We'll of course try to get the interface right at the first
> > > >  > try. OTOH... if wrong interface is in kernel for a month, I do not
> > > >  > think it is reasonable to keep supporting that wrong interface for a
> > > >  > year before it can be removed. One month of warning should be fair in
> > > >  > such case...
> > > > 
> > > > Users want to be able to boot between different kernels.
> > > > Tying functionality to specific versions of userspace completely
> > > > screws them over.
> > > 
> > > Well, by the time we have any _users_ interface should be
> > > stable. Actually I believe interface will be stable from day 0, but...
> > >
> > I'm sure gregkh thought the same thing with about sysfs and udev and we've
> > seen how well that's worked out...
> 
> Well, that was just an unfortunate "bug".
> 
> Declaring interfaces "stable" makes as much sense as all the other
> tries to define crazy enterprise "standards" nobody follows in real
> world.
> 
> In a developing environment, interfaces _become_ stable and don't get
> _declared_ by anybody as such. We are not talking about syscall
> interfaces or things that are simple enough to be kept stable, if you
> cross a certain level of complexity, you just can't apply these rules
> anymore.
> 
> Interfaces mature over the time they get used. Only the _use_ of it
> collects the needed information to form the model behind it. They get
> improved up to the point that changing the interface causes more
> pain than it's worth this change. Then an interface has _become_ "stable"
> cause it makes sense at that point.

Agreed.

> "by the time we have any _users_ interface should be stable", that's
> such a nonsense. If you don't have any user, you don't know if this
> interface works at all and only if it gets used you get the needed
> feedback to improve it.

I think Pavel meant "users who don't work on it themselves".

Greetings,
Rafael

  reply	other threads:[~2006-01-27 11:22 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-24  8:29 Rafael J. Wysocki
2006-01-24 11:14 ` Pavel Machek
2006-01-24 21:13 ` Andrew Morton
2006-01-24 21:30   ` Pavel Machek
2006-01-24 21:58     ` Andrew Morton
2006-01-24 22:14       ` Pavel Machek
2006-01-24 22:20         ` Dave Jones
2006-01-24 22:33           ` Pavel Machek
2006-01-24 22:38             ` Dave Jones
2006-01-24 22:44               ` Pavel Machek
2006-01-26  2:09                 ` Jim Crilly
2006-01-26  7:58                   ` Pavel Machek
2006-01-27  1:11                   ` Greg KH
2006-01-27  3:42                   ` Kay Sievers
2006-01-27 11:24                     ` Rafael J. Wysocki [this message]
2006-01-24 22:47               ` Lee Revell
2006-01-24 23:53         ` Rafael J. Wysocki
2006-01-25  0:17           ` Andrew Morton
2006-01-25  0:31             ` Rafael J. Wysocki
2006-01-24 23:35   ` Rafael J. Wysocki
2006-01-25  2:46     ` Benjamin LaHaise
2006-01-25 10:50       ` Rafael J. Wysocki
2006-01-25 12:18     ` Pavel Machek
2006-01-25 12:29       ` Rafael J. Wysocki
2006-01-25 12:20     ` Pavel Machek

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=200601271224.12983.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=akpm@osdl.org \
    --cc=davej@redhat.com \
    --cc=kay.sievers@vrfy.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    /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

all inboxes | Powered by JetHome®