| To: | "arun4linux" <arun4linux@xxxxxxxxxxxxxx>, "Michael Richardson" <mcr@xxxxxxxxxxxxxxxxxxxxxx>, netdev@xxxxxxxxxxx, "Linux Kernel Mailing List" <linux-kernel@xxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: Re: pci-skeleton duplex check |
| From: | "Aravind Ceyardass" <aravind1001@xxxxxxxxxxxxx> |
| Date: | Mon, 16 Dec 2002 14:55:13 -0400 |
| Cc: | aravind1001@xxxxxxxxxxxxx |
| In-reply-to: | <200212141428.TAA32351@WS0005.indiatimes.com> |
| References: | <200212141428.TAA32351@WS0005.indiatimes.com> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
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 |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | 2.4.20, tg3 , and 5704, Larry Sendlosky |
|---|---|
| Next by Date: | Re: Mailling list archive URL broken?, Ralf Baechle |
| Previous by Thread: | Re: Re: pci-skeleton duplex check, Steffen Persvold |
| Next by Thread: | deepspace6 official announcement, Mauro Tortonesi |
| Indexes: | [Date] [Thread] [Top] [All Lists] |