Sebastian Harl <[EMAIL PROTECTED]> wrote Thu, Sep 11, 2008:
> Hi,
>
> On Thu, Sep 11, 2008 at 06:02:47PM +0200, Gerfried Fuchs wrote:
> > tig claims to use options that git-log and git-diff does, too. So far,
> > so good. tig --author=foo seems to be proper - at least, from a first
> > glance. After scrolling down a fair bit it starts to list bogous commits
> > that neither match nor are in chronological order, rather the contrary:
> > they raise in time again? git-log --author=foo shows the proper thing.
>
> I could reproduce that with the following commands:
>
> git clone git://git.verplant.org/collectd.git
> tig --author="Sebastian Harl" # bogus output
> git log --author="Sebastian Harl" # correct output
>
> I might have some time to look into this tomorrow if Jonas is not faster
> than me ;-)
The reason is that tig by default asks git-log for boundary commits
(using the --boundary flag). The reason the output looks bogus is that
git-log prints boundary commits at the end of the output and tig doesn't
do any reordering. If you run tig like this:
TIG_MAIN_CMD="git log --pretty=raw --author=Sebastian" tig
You should get the expected result.
Regarding a fix, either there should maybe be a flag and/or option to
disable boundary commits or tig should be changed to reorder the
commits.
--
Jonas Fonseca
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
