lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20080525.225339.94300435.davem@davemloft.net>
Date:	Sun, 25 May 2008 22:53:39 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	mcarlson@...adcom.com
Cc:	netdev@...r.kernel.org, mchan@...adcom.com, benli@...adcom.com
Subject: Re: Version numbering

From: "Matt Carlson" <mcarlson@...adcom.com>
Date: Fri, 23 May 2008 12:32:10 -0700

> Hi David.  I'm sitting on a small patchset of bugfixes destined for the
> net-2.6 tree, but I'm a little confused about how I should handle the
> version numbering.
> 
> Right now, the net-2.6 tg3 driver is at version 3.92.  The net-next-2.6
> tree has 5785 support added and has a version of 3.93.  If we apply
> these patches to the net-2.6 driver, we will want to increase the
> version number.  How would you prefer we handle this?

Maybe what we can do is add another sub-version field.  So the stable
bug fixed driver in net-2.6 would end up being 3.92.1 or something
like that.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ