From: Jeff Garzik <jeff@garzik.org>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: "David Miller" <davem@davemloft.net>,
jeffrey.t.kirsher@intel.com, shemminger@vyatta.com,
netdev@vger.kernel.org, gospo@redhat.com,
peter.p.waskiewicz.jr@intel.com,
"Aníbal Monsalve Salazar" <anibal@debian.org>
Subject: Re: [ethtool PATCH] ethtool: Add Direct Attach to the available connector ports
Date: Wed, 23 Dec 2009 17:52:08 -0500 [thread overview]
Message-ID: <4B329F18.4070607@garzik.org> (raw)
In-Reply-To: <1259584513.3709.173.camel@localhost>
On 11/30/2009 07:35 AM, Ben Hutchings wrote:
> On Sun, 2009-11-29 at 05:42 -0500, Jeff Garzik wrote:
>> The current scheme just increments a release number: 5->6, 6->7, etc.
>> But with so few kernel releases (and thus ethtool releases), I was
>> leaning towards either yearly release naming ("ethtool-2009"), kernel
>> release naming ("ethtool-2.6.33"), or the release scheme proposed for
>> glibc: snapshot directly from the git repository.
> I think it should be based on kernel versions, so that it's clear
> whether a given ethtool version supports the features introduced in a
> given kernel version.
Sounds like kernel version it is. Will debut ethtool-2.6.33 in a week
or so, then. I posted ethtool-2.6.33-pre1 just now (intentionally
different from 2.6.33-rc1, to hint that ethtool release candidates need
not march in lock step with kernel pre-releases). Let some bug fixes
trickle in, and then release ethtool-2.6.33.
Jeff
next prev parent reply other threads:[~2009-12-23 22:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-25 10:13 [ethtool PATCH] ethtool: Add Direct Attach to the available connector ports Jeff Kirsher
2009-11-29 8:36 ` David Miller
2009-11-29 10:42 ` Jeff Garzik
2009-11-29 18:35 ` Peter P Waskiewicz Jr
2009-11-30 12:35 ` Ben Hutchings
2009-12-23 22:52 ` Jeff Garzik [this message]
2009-11-29 11:03 ` Jeff Garzik
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=4B329F18.4070607@garzik.org \
--to=jeff@garzik.org \
--cc=anibal@debian.org \
--cc=ben@decadent.org.uk \
--cc=davem@davemloft.net \
--cc=gospo@redhat.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=netdev@vger.kernel.org \
--cc=peter.p.waskiewicz.jr@intel.com \
--cc=shemminger@vyatta.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).