netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Aravind Ceyardass" <aravind1001@speedpost.net>
To: "arun4linux" <arun4linux@indiatimes.com>,
	"Michael Richardson" <mcr@sandelman.ottawa.on.ca>,
	netdev@oss.sgi.com,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Cc: aravind1001@speedpost.net
Subject: Re: Re: pci-skeleton duplex check
Date: Mon, 16 Dec 2002 14:55:13 -0400	[thread overview]
Message-ID: <20021216185513.43F023D56F@server2.fastmail.fm> (raw)
In-Reply-To: <200212141428.TAA32351@WS0005.indiatimes.com>


Hi,

A good scheme for numbering kernels or software components in general is
as follows

For stable releases. (x.even.y=major.minor.patch)

increment patch for any bug fixes.
increment minor for any enhancements or new interfaces.
increment major for interface changes or interface deletions.(dangerous
or poor design)

We should increment major even if interface remains same but behaviour
has changed.(again may be poor design)

For development releases we can't follow the above scheme, because the
interfaces are in a flux and we may end up
in version 589.201.700 from 2.4.20. So, we decide to increment patch
number for all changes and deletions.

Hope it helps!

Regards

Aravind


-- 
http://fastmail.fm - IMAP accessible web-mail

  parent reply	other threads:[~2002-12-16 18:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-14 14:35 Re: pci-skeleton duplex check arun4linux
2002-12-14 16:14 ` Russell King
2002-12-14 21:26   ` Mr. James W. Laferriere
2002-12-15  0:37   ` Steffen Persvold
2002-12-16 18:55 ` Aravind Ceyardass [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-12-14 14:35 arun4linux

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=20021216185513.43F023D56F@server2.fastmail.fm \
    --to=aravind1001@speedpost.net \
    --cc=arun4linux@indiatimes.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mcr@sandelman.ottawa.on.ca \
    --cc=netdev@oss.sgi.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).