linux-kernel - Removal of staging/rt2860sta (and rt2870sta)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 08 Apr 2011 09:53:57 -0500
From:	Larry Finger <Larry.Finger@...inger.net>
To:	Greg Kroah-Hartman <gregkh@...e.de>
CC:	wireless <linux-wireless@...r.kernel.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Removal of staging/rt2860sta (and rt2870sta)

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?

Thanks,

Larry

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/