From: "Dirk Süsserott" <newsletter@dirk.my1.cc>
To: Martin von Zweigbergk <martin.von.zweigbergk@gmail.com>
Cc: Pat Thoyts <patthoyts@users.sourceforge.net>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: Gitk: shortcut to jump to the current HEAD (yellow spot)?
Date: Sun, 25 Dec 2011 20:33:33 +0100 [thread overview]
Message-ID: <4EF77A8D.7020907@dirk.my1.cc> (raw)
In-Reply-To: <CAOeW2eGCKxYW1TT-HPoSCO0_PsQPX5C-bcHLUy73MTd7=CsqRA@mail.gmail.com>
Am 24.12.2011 05:22 schrieb Martin von Zweigbergk:
> 2011/12/23 Dirk Süsserott <newsletter@dirk.my1.cc>:
>>
>> That's because gitk behaves odd (at least to me) when not run from the
>> top-level directory. E.g. the "touching paths" box won't find files in
>> the top dir if you don't prefix them with a slash.
>
> This should be fixed in c332f44 (gitk: Fix file highlight when run in
> subdirectory, 2011-04-04), which is in the current master and thus, I
> believe, to be released in Git 1.7.9.
>
> Martin
Ahh, cool. I wouldn't have noticed because I'm so used to my "cd $TOP &&
gitk". I thought it was by intention because it just behaves like "git
log": When run from subdirs it doesn't know about topdir files: Assume
README.txt is in the topdir and current dir is some subdir:
$ git log -- README.txt # fails
$ git log -- ../README.txt # works
My alias (or function) was just a helper to avoid remembering where I
started gitk from.
Cheers,
Dirk
BTW, Merry X-Mas to you and all others on the list :-)
prev parent reply other threads:[~2011-12-25 19:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-22 15:49 Gitk: shortcut to jump to the current HEAD (yellow spot)? Dirk Süsserott
2011-12-22 17:09 ` Martin von Zweigbergk
2011-12-22 17:23 ` Dirk Süsserott
2011-12-22 18:26 ` Pat Thoyts
2011-12-23 18:54 ` Dirk Süsserott
2011-12-24 4:22 ` Martin von Zweigbergk
2011-12-25 19:33 ` Dirk Süsserott [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=4EF77A8D.7020907@dirk.my1.cc \
--to=newsletter@dirk.my1.cc \
--cc=git@vger.kernel.org \
--cc=martin.von.zweigbergk@gmail.com \
--cc=patthoyts@users.sourceforge.net \
/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).