linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Theodore Ts'o <tytso@mit.edu>
To: Adrian Chadd <adrian@freebsd.org>
Cc: Christian Lamparter <chunkeey@googlemail.com>,
	Eugene Krasnikov <k.eugene.e@gmail.com>,
	Kalle Valo <kvalo@adurom.com>,
	"Luis R. Rodriguez" <mcgrof@do-not-panic.com>,
	linux-bluetooth <linux-bluetooth@vger.kernel.org>,
	linux-wireless <linux-wireless@vger.kernel.org>,
	ath9k_htc_fw <ath9k_htc_fw@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Version number policy!
Date: Tue, 9 Apr 2013 07:28:24 -0400	[thread overview]
Message-ID: <20130409112824.GA12050@thunk.org> (raw)
In-Reply-To: <CAJ-VmokQ=1FLnn-0Ew1JTY_WhYuSYmZq2=DuNTV0TR3kF4wo7g@mail.gmail.com>

On Mon, Apr 08, 2013 at 06:51:10PM -0700, Adrian Chadd wrote:
> 
> But then you end up with people making filesystems which aren't
> necessarily backwards compatible (and aren't aware of this), then try
> to share with other extX implementations; or boot an older Linux
> kernel (eg plugging an ext3 device on a newer box to an older box.)
> Now, ext3 is a bit more mature nowdays so people aren't _always_
> hitting this corner case.

You have a long memory --- going back to about seven years ago, to
2006....

> I'm not knocking extX here; I'm just pointing out that exposing things
> as a set of capability flags doesn't magically fix interoperability.
> It just stops you from scribbling crap where it shouldn't be.

Sure, the only question is how long do you support ancient file
systems out there.  I consider that primarily a distribution question,
not an upstream development question.  People who pay $$$ for ancient
crud, expect that the people to whom they have paid $$$ will take care
of that problem for them.  From an upstream development perspective,
some people might argue that two years is plenty of time to wait for
the vast majority of the people running community distributions to
have upgraded (and if they want more than that, they can pay $$$ to
the aforementioned enterprise distro's, or take care of that situation
on their own).

						- Ted

      reply	other threads:[~2013-04-09 11:28 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAJ-Vmo=LVSzdEo6DhfOVT_0JHCTMmdPU1zGfMuBmhmr8QuDmJQ@mail.gmail.com>
2013-04-05  8:19 ` Version number policy! Luis R. Rodriguez
2013-04-05  8:21   ` Adrian Chadd
2013-04-05 16:42     ` Eugene Krasnikov
2013-04-05 17:03   ` Christian Lamparter
2013-04-05 17:23     ` Eugene Krasnikov
2013-04-05 18:08       ` Christian Lamparter
2013-04-05 19:16         ` Adrian Chadd
2013-04-06  5:52       ` Kalle Valo
2013-04-06  7:08         ` Adrian Chadd
2013-04-08  9:10           ` Eugene Krasnikov
2013-04-08 15:33             ` Christian Lamparter
2013-04-08 19:00               ` Adrian Chadd
2013-04-08 20:37                 ` Eugene Krasnikov
2013-04-08 22:03                   ` Christian Lamparter
2013-04-08 23:12                     ` Adrian Chadd
2013-04-09  0:37                       ` Theodore Ts'o
2013-04-09  1:51                         ` Adrian Chadd
2013-04-09 11:28                           ` Theodore Ts'o [this message]

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=20130409112824.GA12050@thunk.org \
    --to=tytso@mit.edu \
    --cc=adrian@freebsd.org \
    --cc=ath9k_htc_fw@lists.infradead.org \
    --cc=chunkeey@googlemail.com \
    --cc=k.eugene.e@gmail.com \
    --cc=kvalo@adurom.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mcgrof@do-not-panic.com \
    /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).