From: Xose Vazquez Perez <xose@wanadoo.es>
To: netdev@oss.sgi.com, linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2.6] pci.ids for e1000
Date: Fri, 12 Sep 2003 21:07:17 +0200 [thread overview]
Message-ID: <3F621965.4070106@wanadoo.es> (raw)
Jeff Garzik wrote:
> The general idea is to keep 2.4, 2.6, and pciids.sf.net in sync.
is there sync between 2.4, 2.6, and pciids.sf.net ? ;-)
Linus and Marcelo should not accept patches against pci.ids,
all updates should go to pciids.sf.net. And every X time
to do a sync with 2.4 and 2.6.
It's the easiest, because otherwise is a chaos and it
takes too much work to do several merges:
2.4 <-> 2.6
2.4 <-> pciids
2.4 <-> 2.6
--
Que trabajen los romanos, que tienen el pecho de lata.
next reply other threads:[~2003-09-12 19:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-12 19:07 Xose Vazquez Perez [this message]
2003-09-30 6:25 ` [PATCH 2.6] pci.ids for e1000 David S. Miller
2003-09-30 23:32 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2003-09-12 20:15 Xose Vazquez Perez
2003-09-12 18:40 Feldman, Scott
2003-09-12 1:11 Feldman, Scott
2003-09-12 16:08 ` 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=3F621965.4070106@wanadoo.es \
--to=xose@wanadoo.es \
--cc=linux-kernel@vger.kernel.org \
--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).