From: "Alex Riesen" <raa.lkml@gmail.com>
To: "Lin Ming" <ming.m.lin@intel.com>
Cc: git@vger.kernel.org, "Moore, Robert" <robert.moore@intel.com>
Subject: Re: git history and file moves
Date: Wed, 22 Oct 2008 13:19:26 +0200 [thread overview]
Message-ID: <81b0412b0810220419q43f6985fs1c608e3d3cbcf8f3@mail.gmail.com> (raw)
In-Reply-To: <1224640967.14280.0.camel@minggr.sh.intel.com>
2008/10/22 Lin Ming <ming.m.lin@intel.com>:
> I'm looking for a way to move files to a new directory and have the
> full history follow the file automatically. Is this possible?
>
> I know about --follow, but I want the history to just follow the file
> transparently. ...
Of all Git tools, what does not do this "transparently" or "automatically"?
How more transparent do you imagine this?
What do you think should follow what?
I ask, because it is hard to understand what exactly is it you're missing:
merge support (which we have), git log listing the files as copied/renamed
(which is what --follow is for, and the suggestion for you is to make an
alias or something), git blame (ever looked at git gui blame?) or gitk
(which follows renames in default configuration)
> Also, we have a git web interface and we want the full
> history for the moved files to be available.
It is available. Whether it is shown is another question. git-web can
be improved (or just configured?)
next prev parent reply other threads:[~2008-10-22 11:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-22 2:02 git history and file moves Lin Ming
2008-10-22 11:19 ` Alex Riesen [this message]
2008-10-22 12:38 ` Michael J Gruber
2008-10-24 21:30 ` Moore, Robert
2008-10-24 21:43 ` Alex Riesen
2008-10-24 22:01 ` Moore, Robert
2008-10-24 22:13 ` Jakub Narebski
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=81b0412b0810220419q43f6985fs1c608e3d3cbcf8f3@mail.gmail.com \
--to=raa.lkml@gmail.com \
--cc=git@vger.kernel.org \
--cc=ming.m.lin@intel.com \
--cc=robert.moore@intel.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).