public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: R.E.Wolff@BitWizard.nl (Rogier Wolff)
To: Andries.Brouwer@cwi.nl
Cc: acahalan@cs.uml.edu, viro@math.psu.edu, alan@lxorguk.ukuu.org.uk,
	linus@transmeta.com, linux-kernel@vger.kernel.org,
	rhw@memalpha.cx, seberino@spawar.navy.mil
Subject: Re: [PATCH] Improved version reporting
Date: Thu, 15 Mar 2001 12:05:09 +0100 (MET)	[thread overview]
Message-ID: <200103151105.MAA24892@cave.bitwizard.nl> (raw)
In-Reply-To: <UTC200103150952.KAA451302.aeb@vlet.cwi.nl> from "Andries.Brouwer@cwi.nl" at "Mar 15, 2001 10:52:25 am"

Andries.Brouwer@cwi.nl wrote:

>     > On Wed, 14 Mar 2001 Andries.Brouwer@cwi.nl wrote:
> 
>     >>> +o  Console Tools      #   0.3.3        # loadkeys -V
>     >>> +o  Mount              #   2.10e        # mount --version
>     >>
>     >> Concerning mount: (i) the version mentioned is too old,

> On the other hand, there are no important changes between
> mount-2.10d and 2.10e, so I see no justification for writing 2.10e.
> It is difficult to say what the "right" version is. There is a
> long series of minor improvements. Probably I would write 2.10r.

Guys, 

How about making a column that says: "recommended". 

So in this case we'd see 2.10r as recommended, but 2.10e as required.

An explanation could state that: 

  if you happen to have the version under "required", but a higher
  version is listed under "recommended", then that newer version is
  available, and but it is likely that one you have will work for
  you. There is no urgent reason to upgrade. But if you happen to be
  upgrading, you are advised upgrade to at least the version in the
  "recommended" column, as that has fixes over the one mentioned in the
  "required" column.

Best regards,

		Roger. 

-- 
** R.E.Wolff@BitWizard.nl ** http://www.BitWizard.nl/ ** +31-15-2137555 **
*-- BitWizard writes Linux device drivers for any device you may have! --*
* There are old pilots, and there are bold pilots. 
* There are also old, bald pilots. 

  reply	other threads:[~2001-03-15 11:06 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-15  9:52 [PATCH] Improved version reporting Andries.Brouwer
2001-03-15 11:05 ` Rogier Wolff [this message]
2001-03-17  4:35 ` Albert D. Cahalan
2001-03-17 17:51   ` Riley Williams
2001-03-19  6:50     ` Albert D. Cahalan
2001-03-19  9:15       ` Riley Williams
2001-03-23  8:33         ` Albert D. Cahalan
2001-03-23  9:42           ` Riley Williams
  -- strict thread matches above, loose matches on Subject: below --
2001-03-17 10:20 Andries.Brouwer
2001-03-17  1:07 Andries.Brouwer
2001-03-17 17:17 ` Riley Williams
2001-03-16 12:45 Andries.Brouwer
2001-03-16 13:30 ` Nick Holloway
2001-03-16 23:28 ` Riley Williams
2001-03-14 19:29 Andries.Brouwer
2001-03-14 23:39 ` Russell King
2001-03-16 10:54 ` Riley Williams
2001-03-14 16:51 Andries.Brouwer
2001-03-14 16:01 Andries.Brouwer
2001-03-14 16:26 ` Alexander Viro
2001-03-15  4:12   ` Albert D. Cahalan
2001-03-14 16:36 ` Henning P. Schmiedehausen
2001-03-14 17:28 ` Riley Williams
     [not found] <11a40b11caeb.11caeb11a40b@nosc.mil>
2001-03-14 10:39 ` Riley Williams

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=200103151105.MAA24892@cave.bitwizard.nl \
    --to=r.e.wolff@bitwizard.nl \
    --cc=Andries.Brouwer@cwi.nl \
    --cc=acahalan@cs.uml.edu \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linus@transmeta.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rhw@memalpha.cx \
    --cc=seberino@spawar.navy.mil \
    --cc=viro@math.psu.edu \
    /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