From: Junio C Hamano <junkio@cox.net>
To: "Marco Costalba" <mcostalba@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [RFC diff-tree -c with copy/rename]
Date: Thu, 17 Aug 2006 21:09:16 -0700 [thread overview]
Message-ID: <7v3bbuelcj.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: e5bfff550608170402w25b9eaeaqe69665bdddaead3c@mail.gmail.com
"Marco Costalba" <mcostalba@gmail.com> writes:
> As example
>
> 'R093MM checkout-index.c builtin-checkout-index.c'
>
> instead of current
>
> 'RM builtin-checkout-index.c'
I am not particularly opposed to have an option to do this. I
originally did not show this because I did not particularly find
it interesting (and I still don't). The output would become a
very long line, not for human consumption, though.
But it should not be too involved if you want to do this. We
already compute all the information necessary to do so before
combine-diff.c::intersect_paths() converts the usual <from,to>
representation (struct diff_filepair) into <result, list of
parents' blobs> representation (struct combine_diff_path), which
is used by combine-diff.c routines.
We currently do not retain that information when this conversion
happens to be used for the output. You would need to add a few
fields to record the preimage filename, similarity score and
status in struct combine_diff_parent and populate them in
intersect_paths() and adjust the output routines.
prev parent reply other threads:[~2006-08-18 4:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-17 11:02 [RFC diff-tree -c with copy/rename] Marco Costalba
2006-08-18 4:09 ` Junio C Hamano [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=7v3bbuelcj.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=mcostalba@gmail.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