From: Jonathan Nieder <jrnieder@gmail.com>
To: Avery Pennarun <apenwarr@gmail.com>
Cc: Nicolas Sebrecht <nicolas.s.dev@gmx.fr>,
Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org
Subject: Re: rfc - Changing the way gitk and git-gui are managed
Date: Sat, 24 Jul 2010 14:34:28 -0500 [thread overview]
Message-ID: <20100724193428.GA4491@burratino> (raw)
In-Reply-To: <AANLkTi=R2-=TNXyFq4OCo6LsYOMNgVga+=6QrAfCoHRx@mail.gmail.com>
Avery Pennarun wrote:
> On Sat, Jul 24, 2010 at 8:54 AM, Jonathan Nieder <jrnieder@gmail.com> wrote:
>> $ git log --oneline -SListbox.font -- gitk-git/gitk
>> $ git log --oneline --follow -SListbox.font -- gitk-git/gitk
>> 62ba514 Move gitk to its own subdirectory
>> $ git log --oneline -SListbox.font -- gitk-git/gitk gitk
>> 207ad7b gitk: Set the font for all listbox widgets
>> $
>
> This is a bug in git log --follow
The first one is not.
> FWIW, I previously tracked the bug down to the fact that it doesn't
> track file renames that happen during a merge commit, which is what
> subtree merge produces. I don't have the time or knowledge required
> to fix it.
Another pointer for interested people:
http://thread.gmane.org/gmane.comp.version-control.git/150727/focus=150796
I prefer to work without --follow, anyway. :)
Hope that helps,
Jonathan
next prev parent reply other threads:[~2010-07-24 19:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-23 2:39 rfc - Changing the way gitk and git-gui are managed Junio C Hamano
2010-07-23 4:04 ` Sverre Rabbelier
2010-07-23 6:16 ` Avery Pennarun
2010-07-27 5:30 ` Jeff King
2010-07-27 5:42 ` Avery Pennarun
2010-07-27 5:46 ` Jeff King
2010-07-27 10:28 ` Jakub Narebski
2010-07-23 6:54 ` Will Palmer
2010-07-25 10:44 ` Sam Vilain
2010-07-23 19:18 ` Greg Troxel
2010-07-24 11:02 ` Nicolas Sebrecht
2010-07-24 12:54 ` Jonathan Nieder
2010-07-24 12:57 ` Jonathan Nieder
2010-07-24 14:00 ` Nicolas Sebrecht
2010-07-24 17:22 ` Jonathan Nieder
2010-07-24 19:18 ` Avery Pennarun
2010-07-24 19:34 ` Jonathan Nieder [this message]
2010-07-25 4:11 ` 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=20100724193428.GA4491@burratino \
--to=jrnieder@gmail.com \
--cc=apenwarr@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=nicolas.s.dev@gmx.fr \
/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.