threads / discuss / 11509

gitk dev branch: F5 gives error after commit

Subject: gitk dev branch: F5 gives error after commit

## tl;dr

3 messages between Jan 7, 2008 and Jan 7, 2008.

replies: 2people: 3as markdown or json

Johannes Sixt· Jan 7, 2008, 16:52 UTC · lore

I use the dev branch of gitk (on Windows), commit 476ca63 (gitk: Index [fnvr]highlights by id rather than row).

1. Start it with:
    gitk --all -300
2. Make a commit.
3. Hit F5. Here I see the error message:
   Error reading commits:
   fatal: bad revision '^-300'

At this time the label of the current branch is already gone from the commit list. There are no other changes made in the display.

Hitting F5 again does nothing. I have to create a new view to get an updated display.

Any help is appreciated. Thanks, -- Hannes

Marco Costalba· Jan 7, 2008, 18:19 UTC · re: Johannes Sixt · lore

Re: gitk dev branch: F5 gives error after commit

On Jan 7, 2008 5:52 PM, Johannes Sixt <j.sixt@viscovery.net> wrote:
Show 13 quoted lines
> I use the dev branch of gitk (on Windows), commit 476ca63 (gitk: Index
> [fnvr]highlights by id rather than row).
>
> 1. Start it with:
>
>     gitk --all -300
>
> 2. Make a commit.
> 3. Hit F5. Here I see the error message:
>
>    Error reading commits:
>    fatal: bad revision '^-300'
>
Windows command line does not handles the  ^ symbol.
Try open a console with cmd.exe and type
git log HEAD^
Marco
Paul Mackerras· Jan 7, 2008, 21:35 UTC · re: Johannes Sixt · lore

Re: gitk dev branch: F5 gives error after commit

Johannes Sixt writes:
Show 12 quoted lines
> I use the dev branch of gitk (on Windows), commit 476ca63 (gitk: Index
> [fnvr]highlights by id rather than row).
> 
> 1. Start it with:
> 
>     gitk --all -300
> 
> 2. Make a commit.
> 3. Hit F5. Here I see the error message:
> 
>    Error reading commits:
>    fatal: bad revision '^-300'

This happens because I naively thought 'git rev-parse --revs-only' would only give me SHA1 IDs. But in any case gitk (on the dev branch) doesn't really do anything much to handle commit selection flags that can't be turned into SHA1 IDs (possibly negated).

Thanks for testing.  I'll fix it.
Paul.

← back to recent threads