From: Jeff Garzik <jeff@garzik.org>
To: David Miller <davem@davemloft.net>
Cc: dlezcano@fr.ibm.com, netdev@vger.kernel.org,
linux-wireless@vger.kernel.org,
John Linville <linville@tuxdriver.com>
Subject: Re: net-2.6.25 is no more...
Date: Thu, 31 Jan 2008 01:09:21 -0500 [thread overview]
Message-ID: <47A16611.3000602@garzik.org> (raw)
In-Reply-To: <20080130.054807.182676684.davem@davemloft.net>
David Miller wrote:
> From: Daniel Lezcano <dlezcano@fr.ibm.com>
> Date: Wed, 30 Jan 2008 10:03:09 +0100
>
>> David Miller wrote:
>>> Now that the bulk has been merged over and we are
>>> actively working alongside Linus's tree I have moved
>>> all current patch applying to net-2.6 instead of net-2.6.25,
>>> so the current tree to use is:
>>>
>>> kernel.org:/pub/scm/linux/kernel/git/davem/net-2.6.git
>> This tree is for fixes only, right ? or shall we send enhancement
>> patches to net-2.6 until net-2.6.26 appears ?
>
> The latter.
So... what to do about changes which are not bug fixes? Such changes
should not go upstream immediately, because that's the standard rule for
merge windows.
And queueing them on our side just re-creates the same old situation we
just changed away from, after all.
Jeff
WARNING: multiple messages have this Message-ID (diff)
From: Jeff Garzik <jeff-o2qLIJkoznsdnm+yROfE0A@public.gmane.org>
To: David Miller <davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
Cc: dlezcano-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org,
netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
John Linville <linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
Subject: Re: net-2.6.25 is no more...
Date: Thu, 31 Jan 2008 01:09:21 -0500 [thread overview]
Message-ID: <47A16611.3000602@garzik.org> (raw)
In-Reply-To: <20080130.054807.182676684.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
David Miller wrote:
> From: Daniel Lezcano <dlezcano-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>
> Date: Wed, 30 Jan 2008 10:03:09 +0100
>
>> David Miller wrote:
>>> Now that the bulk has been merged over and we are
>>> actively working alongside Linus's tree I have moved
>>> all current patch applying to net-2.6 instead of net-2.6.25,
>>> so the current tree to use is:
>>>
>>> kernel.org:/pub/scm/linux/kernel/git/davem/net-2.6.git
>> This tree is for fixes only, right ? or shall we send enhancement
>> patches to net-2.6 until net-2.6.26 appears ?
>
> The latter.
So... what to do about changes which are not bug fixes? Such changes
should not go upstream immediately, because that's the standard rule for
merge windows.
And queueing them on our side just re-creates the same old situation we
just changed away from, after all.
Jeff
next prev parent reply other threads:[~2008-01-31 6:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-30 5:22 net-2.6.25 is no more David Miller
2008-01-30 9:03 ` Daniel Lezcano
2008-01-30 13:48 ` David Miller
2008-01-30 17:38 ` Daniel Lezcano
2008-01-30 18:29 ` Arnaldo Carvalho de Melo
2008-01-30 19:16 ` Daniel Lezcano
2008-01-31 0:36 ` David Miller
2008-01-31 6:09 ` Jeff Garzik [this message]
2008-01-31 6:09 ` Jeff Garzik
2008-01-31 6:21 ` David Miller
2008-01-31 6:21 ` David Miller
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=47A16611.3000602@garzik.org \
--to=jeff@garzik.org \
--cc=davem@davemloft.net \
--cc=dlezcano@fr.ibm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.