From: Junio C Hamano <gitster@pobox.com>
To: "Mikhail T." <mi+thun@aldan.algebra.com>
Cc: Johannes Sixt <j6t@kdbg.org>, git@vger.kernel.org
Subject: Re: How to fork a file (git cp ?)
Date: Wed, 04 May 2011 19:14:24 -0700 [thread overview]
Message-ID: <7v1v0ddhbz.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <4DC20461.4090703@aldan.algebra.com> (Mikhail T.'s message of "Wed, 04 May 2011 21:58:57 -0400")
"Mikhail T." <mi+thun@aldan.algebra.com> writes:
> On 04.05.2011 17:02, Junio C Hamano wrote:
>> Well, if you come from the mindset that a "file" has an identity (hence
>> there is a distinction between "This file used to be called A and at one
>> point was renamed to B which is the name we see today" and "Some time ago
>> somebody created a file B with the same contents as A and then removed A
>> at the same time"), "copy" would not make much sense. What identity does
>> a new file B gets when you create it by copying from A?
> What I want is to signify something like: "This code was obtained from
> that in file A."
I think that is what exactly "blame -C -C" gives you.
next prev parent reply other threads:[~2011-05-05 2:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-04 17:56 How to fork a file (git cp ?) Mikhail T.
2011-05-04 18:16 ` Johannes Sixt
2011-05-04 18:22 ` Johannes Sixt
2011-05-04 19:05 ` Stephen Bash
2011-05-04 19:17 ` Mikhail T.
2011-05-04 20:36 ` Øyvind A. Holm
2011-05-04 21:02 ` Junio C Hamano
2011-05-05 1:58 ` Mikhail T.
2011-05-05 2:14 ` Junio C Hamano [this message]
2011-05-05 18:02 ` Piotr Krukowiecki
2011-05-05 18:50 ` Junio C Hamano
2011-05-05 19:27 ` Piotr Krukowiecki
2011-05-05 19:31 ` Mikhail T.
2011-05-05 20:01 ` Jeff King
2011-05-05 20:01 ` Piotr Krukowiecki
2011-05-05 20:06 ` Piotr Krukowiecki
2011-05-05 20:07 ` Jeff King
2011-05-08 19:40 ` Pete Harlan
2011-05-08 20:03 ` Junio C Hamano
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=7v1v0ddhbz.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=j6t@kdbg.org \
--cc=mi+thun@aldan.algebra.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;
as well as URLs for NNTP newsgroup(s).