gitk run from subdir and "find commit touching paths"

3 messages, 2 authors, 2016-06-15 · open the first message on its own page

gitk run from subdir and "find commit touching paths"

From: Sitaram Chamarty <hidden>
Date: 2016-06-15 22:46:02

If I run gitk from a subdirectory, and then try to find a
commit touching a path, it doesn't work.  No movement of
cursor on "Next/Prev".

Running from the main project directory makes it work ok --
you can go "Next" or "Prev" finding other commits that
touched the same path.

Is this a known problem?  I couldn't find it in the mailing
list archives.

Thanks,

Sitaram

Re: gitk run from subdir and "find commit touching paths"

From: Matt Graham <hidden>
Date: 2016-06-15 22:46:04

On Tue, Jan 27, 2009 at 12:14, Sitaram Chamarty [off-list ref] wrote:
If I run gitk from a subdirectory, and then try to find a
commit touching a path, it doesn't work.  No movement of
cursor on "Next/Prev".

Running from the main project directory makes it work ok --
you can go "Next" or "Prev" finding other commits that
touched the same path.

Is this a known problem?  I couldn't find it in the mailing
list archives.
Hi,
I get this too.  My repos are small enough that I'm usually able to
just cd to the root dir and rerun gitk.

Re: gitk run from subdir and "find commit touching paths"

From: Sitaram Chamarty <hidden>
Date: 2016-06-15 22:46:04

On 2009-01-30, Matt Graham [off-list ref] wrote:
On Tue, Jan 27, 2009 at 12:14, Sitaram Chamarty [off-list ref] wrote:
I get this too.  My repos are small enough that I'm usually able to
just cd to the root dir and rerun gitk.
Mine are too; and if they weren't I'd alias it in bash, no
sweat.  It was just a question to see if it was a known
problem, and really all I wanted was to confirm what I am
seeing.

I'm not even saying it needs to be fixed :-)
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help