From: Dan Williams <dcbw@redhat.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Please pull 'master' branch of libertas (for 2.6.22)
Date: Thu, 10 May 2007 10:35:13 -0400 [thread overview]
Message-ID: <1178807713.23307.1.camel@localhost.localdomain> (raw)
In-Reply-To: <20070510013523.GA4544@tuxdriver.com>
On Wed, 2007-05-09 at 21:35 -0400, John W. Linville wrote:
> On Wed, May 09, 2007 at 05:16:14PM -0400, Dan Williams wrote:
>
> > This is latest libertas git and should be pushed to 2.6.22. It takes
> > care of a few of Christoph's objections, including ioctl removal,
> > version.h removal, and debug define cleanups.
> >
> > git://git.infradead.org/libertas-2.6.git
>
> Dan,
>
> There is a problem...the libertas-2.6 tree doesn't have a "clean"
> history. It appears to have the entire development history of the
> libertas project. We need something more concise and "sanitized"
> for pushing upstream.
Yeah; that sucks. I've pulled wireless-2.6 and I'm adding
cleanup/review patches now. What I may not be able to do, depending on
time, is fix the warnings and sparse stuff Randy brought up.
Dan
> We do not really want the patches for new development, at least not
> for 2.6.22. Could you help identify which patches in the history
> correspond to review fixes?
>
> I can generate a single diff, but it is huge ("34 files changed, 3069
> insertions(+), 5643 deletions(-)") and it isn't clear to me that it
> is only cleanups. Perhaps you could split this up into a few separate
> patches? Especially those patches specific to review comments?
>
> I'm sorry...I know this is a PITA. I appreciate your effort and
> cooperation.
>
> John
next prev parent reply other threads:[~2007-05-10 14:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-09 21:16 Please pull 'master' branch of libertas (for 2.6.22) Dan Williams
2007-05-10 1:35 ` John W. Linville
2007-05-10 14:35 ` Dan Williams [this message]
2007-05-10 19:27 ` Dan Williams
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=1178807713.23307.1.camel@localhost.localdomain \
--to=dcbw@redhat.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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).