From: Linus Torvalds <torvalds@linux-foundation.org>
To: Dominik Brodowski <linux@dominikbrodowski.net>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
netdev@vger.kernel.org, Komuro <komurojun-mbn@nifty.com>
Subject: Re: [PATCH] pcmcia: xirc2ps_cs bugfix
Date: Fri, 13 Aug 2010 16:48:52 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.2.00.1008131641230.17306@i5.linux-foundation.org> (raw)
In-Reply-To: <20100813185623.GC5853@comet.dominikbrodowski.net>
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
prev parent reply other threads:[~2010-08-13 23:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-13 18:56 [PATCH] pcmcia: xirc2ps_cs bugfix Dominik Brodowski
2010-08-13 23:48 ` Linus Torvalds [this message]
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=alpine.LFD.2.00.1008131641230.17306@i5.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=komurojun-mbn@nifty.com \
--cc=linux@dominikbrodowski.net \
--cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox