From: Joshua Jensen <jjensen@workspacewhiz.com>
To: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Following history of a copied file from another indirect branch
Date: Thu, 21 Oct 2010 12:47:01 -0600 [thread overview]
Message-ID: <4CC08AA5.8070502@workspacewhiz.com> (raw)
It has become a necessity to copy a file from one long-lived branch to
another. It is not possible to merge the branches at this time.
I would like to have 'git gui blame' follow the copy back through its
original history, but I don't believe Git has metadata for storing
this. Something along the lines of a 'followparent' in the commit
object, for instance, would allow the revision walking code to wander
the history down an alternate line.
By comparison, integrates work at a file level in Perforce. That means
I can integrate a file from one branch to another, and parentage is
stored such that I can follow the file back through its history.
Are there any facilities to do this now?
Thanks!
Josh
next reply other threads:[~2010-10-21 18:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-21 18:47 Joshua Jensen [this message]
2010-10-21 19:39 ` Following history of a copied file from another indirect branch Brian Gernhardt
2010-10-21 20:06 ` Joshua Jensen
2010-10-22 6:35 ` Johannes Sixt
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=4CC08AA5.8070502@workspacewhiz.com \
--to=jjensen@workspacewhiz.com \
--cc=git@vger.kernel.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).