From: Graeme Geldenhuys <graemeg@gmail.com>
To: git@vger.kernel.org
Subject: Re: Proper tracking of copies in git log and others
Date: Tue, 07 Jul 2009 08:53:44 +0200 [thread overview]
Message-ID: <h2ure0$j73$1@ger.gmane.org> (raw)
In-Reply-To: <4A4F8258.5070701@trn.iki.fi>
Lasse Kärkkäinen wrote:
> Getting full history of a file, including that beyond copies, is rather
> important and apparently not currently supported by git tools.
You seem to be right. I'm quite new to Git so don't know all the
commands, but this is what I came up with..
$ git log --raw 2009/exercise2/description.txt
commit edfd954572e844b05a7489bcaa149afb679bc1f6
Author: Graeme Geldenhuys <graeme@mastermaths.co.za>
Date: Tue Jul 7 08:44:20 2009 +0200
Course 2009 recycled entirely from 2008
:000000 100644 0000000... e965047... A 2009/exercise2/description.txt
We then take note of the ^^^^^^^ value and generate the following
command.
$ git log -C --raw | grep e965047
:000000 100644 0000000... e965047... A 2009/exercise2/description.txt
:000000 100644 0000000... e965047... A 2008/exercise2/description.txt
:000000 100644 0000000... e965047... A 2007/exercise1/description.txt
Now now shows you the history of the file as it was copied from one
directory to another.
Regards,
- Graeme -
--
fpGUI Toolkit - a cross-platform GUI toolkit using Free Pascal
http://opensoft.homeip.net/fpgui/
next prev parent reply other threads:[~2009-07-07 6:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-04 16:24 Proper tracking of copies in git log and others Lasse Kärkkäinen
2009-07-04 18:31 ` Sean Estabrooks
2009-07-14 12:19 ` Lasse Kärkkäinen
2009-07-07 6:53 ` Graeme Geldenhuys [this message]
2009-07-07 13:48 ` Michael J Gruber
2009-07-07 14:59 ` Avery Pennarun
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='h2ure0$j73$1@ger.gmane.org' \
--to=graemeg@gmail.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).