From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: [PATCH] apply --unidiff-zero: loosen sanity checks for --unidiff=0 patches
Date: Sun, 17 Sep 2006 10:30:52 +0200 [thread overview]
Message-ID: <eej12j$36t$2@sea.gmane.org> (raw)
In-Reply-To: 7vsliq7vqr.fsf_-_@assigned-by-dhcp.cox.net
Junio C Hamano wrote:
> This adds a new flag, --unified-zero, to allow bypassing these
> checks. If you are in control of the patch generation process,
> you should not use --unified=0 patch and fix it up with this
> flag; rather you should try work with a patch with context. But
> if all you have to work with is a patch without context, this
> flag may come handy as the last resort.
Doesn't -C0 option to git-apply bypass those checks?
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next prev parent reply other threads:[~2006-09-17 8:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-15 13:22 git-apply fails to apply some patches Gerrit Pape
2006-09-17 6:16 ` Junio C Hamano
2006-09-17 8:17 ` [PATCH] apply --unidiff-zero: loosen sanity checks for --unidiff=0 patches Junio C Hamano
2006-09-17 8:30 ` Jakub Narebski [this message]
2006-09-17 8:49 ` Junio C Hamano
2006-09-17 9:01 ` Jakub Narebski
2006-09-17 9:50 ` Junio C Hamano
2006-09-17 10:55 ` [PATCH] git-apply(1): document --unidiff-zero Jonas Fonseca
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='eej12j$36t$2@sea.gmane.org' \
--to=jnareb@gmail.com \
--cc=git@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;
as well as URLs for NNTP newsgroup(s).