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]
Date:	Fri, 13 Aug 2010 16:48:52 -0700 (PDT)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Dominik Brodowski <linux@...inikbrodowski.net>
cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	netdev@...r.kernel.org, Komuro <komurojun-mbn@...ty.com>
Subject: Re: [PATCH] pcmcia: xirc2ps_cs bugfix



On Fri, 13 Aug 2010, Dominik Brodowski wrote:
> 
> could you apply the attached bugfix for PCMCIA, please? Alternatively,
> please pull from 
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/brodo/pcmcia-2.6.git master
> 
> where this one patch is located. What do you prefer, actually, if it is just
> one patch I want to push to you?

Doesn't really matter. These days, my workflow is so git-centric that a 
simple "git pull" is a tiny simpler just because it's what I do day in and 
day out, and doesn't involve exporting a patch and applying it - but the 
difference is really so small that it matters not at all. And applying the 
patch as a patch avoids a sily merge for a trivial change.

So it really can go both ways. I'll take the patch this time, because I 
happened to be in my "gather up patches" mode (which in turn is mostly 
because your subject said "PATCH" rather than "GIT PULL" - I had ignored 
the email while in my "git pull" phase). Which just goes to show how 
little I care, and how small details make me do one over the other.

So I think you should just base it on how convenient it is for you. 

But if you have even just two patches, I probably prefer a "git pull". 
But again, it's not a big deal.

                    Linus
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ