From: Avery Pennarun <apenwarr@gmail.com>
To: Jonathan Nieder <jrnieder@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: Sun, 25 Jul 2010 00:11:37 -0400 [thread overview]
Message-ID: <AANLkTikkMYY5r4RzBZ-mTBVSXuZfhu8HSZPEbNTGnJ2i@mail.gmail.com> (raw)
In-Reply-To: <20100724193428.GA4491@burratino>
On Sat, Jul 24, 2010 at 3:34 PM, Jonathan Nieder <jrnieder@gmail.com> wrote:
> 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.
That one is a bug in history simplification, which has simplified away
commits that affected files that got renamed into gitk-git/gitk during
a merge commit. So the bug is very similar, albeit probably in a
different place in the code. (-M doesn't help either.)
Avery
prev parent reply other threads:[~2010-07-25 4:12 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
2010-07-25 4:11 ` Avery Pennarun [this message]
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=AANLkTikkMYY5r4RzBZ-mTBVSXuZfhu8HSZPEbNTGnJ2i@mail.gmail.com \
--to=apenwarr@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@gmail.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 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).