From: "Sam Liddicott" <sam@liddicott.com>
To: Nanako Shiraishi <nanako3@lavabit.com>
Cc: git@vger.kernel.org
Subject: Re: let git-diff allow patch to delete empty files?
Date: Thu, 06 Nov 2008 08:30:24 -0000 [thread overview]
Message-ID: <4912AB20.4070608@liddicott.com> (raw)
In-Reply-To: 20081106060940.6117@nanako3.lavabit.com
* Nanako Shiraishi wrote, On 05/11/08 21:09:
> Quoting "Sam Liddicott" <sam@liddicott.com>:
>
>
>> In some cases "patch" cannot apply diff's generated using git-diff, I've
>> had a "git diff" output look like this when an empty file was removed as
>> the only change:
>>
>
> Even if you do not use git to manage your changes, you can use "git apply" from outside of a git repository as a replacement for "patch".
>
>
Good tip, thanks.
In this case it is rpmbuild that is doing the patching, and making git a
build-requires would not be popular.
Sam
prev parent reply other threads:[~2008-11-06 8:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-05 12:22 let git-diff allow patch to delete empty files? Sam Liddicott
2008-11-05 14:49 ` Sam Liddicott
2008-11-05 21:09 ` Nanako Shiraishi
2008-11-06 8:30 ` Sam Liddicott [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=4912AB20.4070608@liddicott.com \
--to=sam@liddicott.com \
--cc=git@vger.kernel.org \
--cc=nanako3@lavabit.com \
/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