linux-kernel - Re: 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-prev] [day] [month] [year] [list]

Message-ID: <20110408205720.GA16065@Pilar.site>
Date:	Fri, 8 Apr 2011 13:57:20 -0700
From:	"Carlos R. Mafra" <crmafra@...il.com>
To:	Larry Finger <Larry.Finger@...inger.net>
Cc:	Greg Kroah-Hartman <gregkh@...e.de>,
	wireless <linux-wireless@...r.kernel.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: Removal of staging/rt2860sta (and rt2870sta)

On Fri,  8 Apr 2011 at  9:53:57 -0500, Larry Finger wrote:
> 
> 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?

I've just remembered about this patch in the git list, which I think
does what you want:

http://thread.gmane.org/gmane.comp.version-control.git/170537/focus=170581

--
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/