From: David Miller <davem@davemloft.net>
To: mcarlson@broadcom.com
Cc: netdev@vger.kernel.org, mchan@broadcom.com, benli@broadcom.com
Subject: Re: Version numbering
Date: Sun, 25 May 2008 22:53:39 -0700 (PDT) [thread overview]
Message-ID: <20080525.225339.94300435.davem@davemloft.net> (raw)
In-Reply-To: <20080523193210.GB26044@localdomain>
From: "Matt Carlson" <mcarlson@broadcom.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.
prev parent reply other threads:[~2008-05-26 5:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-23 19:32 Version numbering Matt Carlson
2008-05-26 5:53 ` David Miller [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=20080525.225339.94300435.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=benli@broadcom.com \
--cc=mcarlson@broadcom.com \
--cc=mchan@broadcom.com \
--cc=netdev@vger.kernel.org \
/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).