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] [thread-next>] [day] [month] [year] [list]
Message-Id: <20090105.201530.195720489.davem@davemloft.net>
Date:	Mon, 05 Jan 2009 20:15:30 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	torvalds@...ux-foundation.org
Cc:	akpm@...ux-foundation.org, netdev@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [GIT]: Networking

From: Linus Torvalds <torvalds@...ux-foundation.org>
Date: Mon, 5 Jan 2009 18:42:19 -0800 (PST)

> On Mon, 5 Jan 2009, David Miller wrote:
> > 
> > Jaswinder Singh (1):
> >       firmware: convert acenic driver to request_firmware()
> 
> Grr. But the old acenic_firmware.h file is left around. Which explains 
> this:
> 
> >  63 files changed, 11470 insertions(+), 1910 deletions(-)
> 
> Ugh. That looks absolutely horrible.
> 
> I pulled, but please take a look at your own diffstats and then ask 
> yourself if things really look like they should look. Because if you had 
> done that, you'd have noticed this.

Sorry, I know how this happened even.

As an aside, is there a way to make git-am and other stuff using the
git patch applying engine to take patches liberally like 'patch'
would?

The default is extremely strict, which makes me check things out by
hand.  That's good, but as I add the change by hand after verifying
it's sanity I often make mistakes that result in things like the above
missed delete, so if I could ask git to be non-strict it would help me
out a lot.

This doesn't excuse me from looking for bogons at my diffstats of
course :)
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ