From: Junio C Hamano <junkio@cox.net>
To: Wolfgang Denk <wd@denx.de>
Cc: git@vger.kernel.org
Subject: Re: Should cg-mkpatch output be usable with cg-patch?
Date: Wed, 20 Jul 2005 20:57:49 -0700 [thread overview]
Message-ID: <7vackgerpe.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20050720234904.B3ED735267C@atlas.denx.de> (Wolfgang Denk's message of "Thu, 21 Jul 2005 01:49:04 +0200")
Wolfgang Denk <wd@denx.de> writes:
> I wander what I should do with "cg-mkpatch" generated output; I had
> the impression that this should be usable with "cg-patch", but these
> are incompatible with each other. Forexample. if a commit contains
> permission changes, my generated patch may look like this:
Yes, cg-patch does grok git extended diff headers, but does it
by hand and missing corner cases like this is understandable.
I only briefly looked at cg-patch, but I suspect that it can
lose 90% lines of its code by just using "git-apply --index".
I see cg-patch wants to be able to do reverse patch, which is
not supported by git-apply currently.
Do people find "cg-patch -R" useful?
next prev parent reply other threads:[~2005-07-21 3:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-20 23:49 Should cg-mkpatch output be usable with cg-patch? Wolfgang Denk
2005-07-21 3:57 ` Junio C Hamano [this message]
2005-07-22 21:02 ` Petr Baudis
2005-07-22 21:03 ` Petr Baudis
2005-07-24 17:50 ` Wolfgang Denk
2005-07-24 22:48 ` Petr Baudis
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=7vackgerpe.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=wd@denx.de \
/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).