From: Kai Blin <kai@samba.org>
To: git@vger.kernel.org
Subject: Re: Directory renames without breaking git log.
Date: Thu, 4 Sep 2008 21:45:09 +0200 [thread overview]
Message-ID: <200809042145.09573.kai@samba.org> (raw)
In-Reply-To: <905315640809031716j7d74d7a6m51b434f62b011135@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1253 bytes --]
On Thursday 04 September 2008 02:16:24 Tarmigan wrote:
> On Wed, Sep 3, 2008 at 2:38 PM, Kai Blin <kai@samba.org> wrote:
> > Unfortunately, the directories are big enough that git log stops to track
> > the renamed files, so e.g. git log ./samba3 does not show the samba3
> > history. The history is not lost, of course, but it's way less intuitive
> > to get it.
>
> You can try setting diff.renamelimit to 0 in your ~/.gitconfig. See
> Linus's email here for a similar situation in the kernel:
> http://lwn.net/Articles/292948/
That doesn't seem to fix "git log path/to/file" cases. The really interesting
part is that if I try git log --follow -M -C path/to/file, I don't get any
history at all. (--follow is the culprit, if I remove that I at least get the
merge commit)
git blame still works, and git log --sparse path/to/file works, of
course. --sparse makes giving a path a bit pointless, of course, but we
probably can live with that for time being. I'm still open for suggestions,
of course. :)
Cheers,
Kai
--
Kai Blin
WorldForge developer http://www.worldforge.org/
Wine developer http://wiki.winehq.org/KaiBlin
Samba team member http://www.samba.org/samba/team/
--
Will code for cotton.
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2008-09-04 19:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-03 21:38 Directory renames without breaking git log Kai Blin
2008-09-04 0:16 ` Tarmigan
[not found] ` <200809040853.36433.kai@samba.org>
2008-09-04 18:35 ` Tarmigan
2008-09-04 19:45 ` Kai Blin [this message]
2008-09-04 19:49 ` Junio C Hamano
2008-09-04 20:52 ` Kai Blin
2008-09-04 22:06 ` Junio C Hamano
2008-09-04 20:41 ` 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=200809042145.09573.kai@samba.org \
--to=kai@samba.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.