From: "Mikhail T." <mi+thun@aldan.algebra.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Johannes Sixt <j6t@kdbg.org>, git@vger.kernel.org
Subject: Re: How to fork a file (git cp ?)
Date: Thu, 05 May 2011 15:31:22 -0400 [thread overview]
Message-ID: <4DC2FB0A.2090100@aldan.algebra.com> (raw)
In-Reply-To: <7v1v0ddhbz.fsf@alter.siamese.dyndns.org>
On 04.05.2011 22:14, Junio C Hamano wrote:
> I think that is what exactly "blame -C -C" gives you.
For that to be useful, one has to suspect, the file was derived by
copying something else... Simple "git log" will not suggest that --
unless the commit message, that adds the new copy of a file points to it...
On 05.05.2011 14:02, Piotr Krukowiecki wrote:
> Maybe Mikhail wanted to say that if there's a git-mv as a shortcut for
> "cp old new ; rm old; add new"
git-mv preserves the old's change-history in new, so it is more than the
above, is not it?
> then there should be a git-cp as a shortcut for
Yes...
-mi
next prev parent reply other threads:[~2011-05-05 19:31 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
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. [this message]
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=4DC2FB0A.2090100@aldan.algebra.com \
--to=mi+thun@aldan.algebra.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=j6t@kdbg.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).