From: "Francis Moreau" <francis.moro@gmail.com>
To: "Linus Torvalds" <torvalds@linux-foundation.org>
Cc: "René Scharfe" <rene.scharfe@lsrfire.ath.cx>,
"Junio C Hamano" <gitster@pobox.com>,
git@vger.kernel.org
Subject: Re: Why doesn't git-apply remove empty file
Date: Thu, 14 Aug 2008 21:42:22 +0200 [thread overview]
Message-ID: <38b2ab8a0808141242k4bd6867dt8ef54f160713061f@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.1.10.0808131602200.3462@nehalem.linux-foundation.org>
On Thu, Aug 14, 2008 at 1:09 AM, Linus Torvalds
<torvalds@linux-foundation.org> wrote:
> and no, git never did that file date thing, so git acts differently from
> GNU patch in this thing (as in so many others, for that matter).
>
Well patch(1) is so used out there that makes git-apply often do the
wrong thing for such corner cases when applying a patch made by
patch(1).
Maybe git-apply would be more friendly regarding patch(1) if it has an
option to emulate GNU patch for some situations. Or if this means
adding too many quirks in git-apply code, maybe give the possibity for
git-am to use patch(1) instead of git-apply.
--
Francis
next prev parent reply other threads:[~2008-08-14 19:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-12 16:17 Why doesn't git-apply remove empty file Francis Moreau
2008-08-13 0:25 ` Junio C Hamano
2008-08-13 7:48 ` Francis Moreau
2008-08-13 21:52 ` René Scharfe
2008-08-13 23:09 ` Linus Torvalds
2008-08-14 19:42 ` Francis Moreau [this message]
2008-08-14 19:57 ` Linus Torvalds
2008-08-14 20:02 ` Linus Torvalds
2008-08-14 20:21 ` Stephan Beyer
2008-08-14 20:54 ` Jeff King
2008-08-14 21:10 ` Stephan Beyer
2008-08-15 4:08 ` Jeff King
2008-08-15 15:53 ` Linus Torvalds
2008-08-14 20:17 ` Francis Moreau
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=38b2ab8a0808141242k4bd6867dt8ef54f160713061f@mail.gmail.com \
--to=francis.moro@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=rene.scharfe@lsrfire.ath.cx \
--cc=torvalds@linux-foundation.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).