From: Greg KH <gregkh@suse.de>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: wireless <linux-wireless@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Removal of staging/rt2860sta (and rt2870sta)
Date: Fri, 8 Apr 2011 09:05:58 -0700 [thread overview]
Message-ID: <20110408160558.GA11902@suse.de> (raw)
In-Reply-To: <4D9F2185.10108@lwfinger.net>
On Fri, Apr 08, 2011 at 09:53:57AM -0500, Larry Finger wrote:
> Greg,
>
> When I looked again at the removal of rt2860sta from staging, it was
> quickly obvious that unless rt2870sta was also removed, very little
> of the code could be removed. As I have no experience with
> rt2800usb, the mainline driver for that device, I went to the
> wireless mailing list with the question. There was one objection to
> the removal, but the maintainers were in favor, thus I will be
> submitting a patch to delete both drivers.
>
> I did the changes on my local git tree, committed them, and used
> 'git format-patch'. I expected that 'git rm' statements would be
> used to delete the files, but I got normal patch format. As a
> result, the resulting patch is over 2.4 GB, and has over 75,000
> lines. Obviously, I'm reluctant to dump a patch of this size on the
> lists. Is there a way to force git to use "rm" statements, or is
> there some way to handle this large patch?
You can point me at the git tree and I can pull from it :)
thanks,
greg k-h
next prev parent reply other threads:[~2011-04-08 16:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-08 14:53 Removal of staging/rt2860sta (and rt2870sta) Larry Finger
2011-04-08 16:05 ` Greg KH [this message]
2011-04-08 20:57 ` Carlos R. Mafra
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=20110408160558.GA11902@suse.de \
--to=gregkh@suse.de \
--cc=Larry.Finger@lwfinger.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@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.