From: Jouni Malinen <j@w1.fi>
To: Dan Williams <dcbw@redhat.com>
Cc: Lars Ericsson <Lars_Ericsson@telia.com>,
'Ivo van Doorn' <ivdoorn@gmail.com>,
hostap@lists.shmoo.com, linux-wireless@vger.kernel.org,
rt2400-devel@lists.sourceforge.net
Subject: Re: [Rt2400-devel] mac80211 / rt2x00 / rt61 and adhoc status
Date: Tue, 19 Aug 2008 20:38:42 +0300 [thread overview]
Message-ID: <20080819173842.GD4805@jm.kir.nu> (raw)
In-Reply-To: <1219088136.2154.11.camel@localhost.localdomain>
On Mon, Aug 18, 2008 at 03:35:36PM -0400, Dan Williams wrote:
> On Mon, 2008-08-18 at 21:27 +0200, Lars Ericsson wrote:
> > I have backported the patches to 0.5.9 and they works fine, as far as I can
> > tell on 2.6.26.
> > I can drop them here if they are of interest. I also vote for putting them
> > into 0.5.x
> >
> > Jouni; would that be possible ?
Sure. I'm usually merging all bug fixes from 0.6.x into the 0.5.x
releases.
> Jouni, if you like I could run through current git HEAD and identify
> some easy candidates for backporting to 0.5.x, and send the 0.6 commit
> ids to the hostap lists for you along with what needs to be done to
> backport the patch.
If the commit messages are clear, i.e., it is obvious that the changes
are bug fixes, I should be able to find these without problems. If there
is any unclarity on the status of the changes, a list could be helpful.
Whenever I'm preparing a new release from a stable branch, I will go
through the git tree and pick all changes that look like bug fixes (with
more filtering for 0.4.x and 0.3.x to only get critical fixes). With
that list, I'm going to be merging the changes in order into the stable
branch. I would expect that the changes discussed here would fall into
this process for automatic (well, with some manual labor ;-) inclusion
into 0.5.x.
--
Jouni Malinen PGP id EFC895FA
prev parent reply other threads:[~2008-08-19 17:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-17 5:36 mac80211 / rt2x00 / rt61 and adhoc status Lars Ericsson
2008-08-17 9:05 ` [Rt2400-devel] " Ivo van Doorn
2008-08-17 9:54 ` Lars Ericsson
2008-08-17 9:58 ` Ivo van Doorn
2008-08-17 10:25 ` Lars Ericsson
2008-08-17 14:02 ` Lars Ericsson
2008-08-17 20:42 ` Lars Ericsson
2008-08-18 14:34 ` Dan Williams
2008-08-18 19:27 ` Lars Ericsson
2008-08-18 19:35 ` Dan Williams
2008-08-19 17:38 ` Jouni Malinen [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=20080819173842.GD4805@jm.kir.nu \
--to=j@w1.fi \
--cc=Lars_Ericsson@telia.com \
--cc=dcbw@redhat.com \
--cc=hostap@lists.shmoo.com \
--cc=ivdoorn@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=rt2400-devel@lists.sourceforge.net \
/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.