From: Greg KH <greg@kroah.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: git@vger.kernel.org
Subject: Re: git applymbox is too anal
Date: Fri, 9 Sep 2005 10:07:56 -0700 [thread overview]
Message-ID: <20050909170756.GB24894@kroah.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0509081754150.3051@g5.osdl.org>
On Thu, Sep 08, 2005 at 05:58:18PM -0700, Linus Torvalds wrote:
>
>
> On Thu, 8 Sep 2005, Greg KH wrote:
> >
> > Or am I missing some option to 'git applymbox' that I can't seem to
> > find?
>
> No. git-apply wants an exact bit-for-bit match. Partly because fuzz is
> hard, but mostly because I don't like it. I apply a _lot_ of patches, and
> if a unforgiving "git-apply" works for me, it should work for you too.
Ok, as I've been using quilt to stage patches before they are ready to
send to you, sometimes, when I build up the final tree, there are tiny
fuzz issues. I'll just make sure to fix this up before running
applymbox in the future.
thanks,
greg k-h
prev parent reply other threads:[~2005-09-09 17:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-08 23:25 git applymbox is too anal Greg KH
2005-09-08 23:39 ` Greg KH
2005-09-09 1:03 ` Junio C Hamano
2005-09-09 0:58 ` Linus Torvalds
2005-09-09 17:07 ` Greg KH [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=20050909170756.GB24894@kroah.com \
--to=greg@kroah.com \
--cc=git@vger.kernel.org \
--cc=torvalds@osdl.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;
as well as URLs for NNTP newsgroup(s).