From: Junio C Hamano <junkio@cox.net>
To: Linus Torvalds <torvalds@osdl.org>
Cc: git@vger.kernel.org
Subject: Re: xdiff: generate "anti-diffs" aka what is common to two files
Date: Wed, 28 Jun 2006 23:04:52 -0700 [thread overview]
Message-ID: <7vbqscwl8b.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: Pine.LNX.4.64.0606282149060.12404@g5.osdl.org
Linus Torvalds <torvalds@osdl.org> writes:
> Junio: the patch that actually _uses_ this comes next. It's based on my
> previous "throw-away" example patches, if you want me to base it on
> something else, please holler.
Nah, I appreciate that you did it this way, because it gave me a
test case to "git-am" your two patches into a temporary branch
and "pull --squash" that into lt/merge-tree branch ;-).
git am ./+LT.mbox
... two patches, applied with --whitespace=strip ...
git tag -f CG
git reset --hard HEAD^^
git pull --squash . tag CG
git commig -C CG
git tag -d CG
next prev parent reply other threads:[~2006-06-29 6:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-29 4:57 xdiff: generate "anti-diffs" aka what is common to two files Linus Torvalds
2006-06-29 6:04 ` Junio C Hamano [this message]
2006-06-29 18:18 ` Davide Libenzi
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=7vbqscwl8b.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--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).