From: Matt Graham <mdg149@gmail.com>
To: Sitaram Chamarty <sitaramc@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: gitk run from subdir and "find commit touching paths"
Date: Fri, 30 Jan 2009 00:56:22 -0500 [thread overview]
Message-ID: <1c5969370901292156k2456b585r8e79889db516bc59@mail.gmail.com> (raw)
In-Reply-To: <slrngnug78.877.sitaramc@sitaramc.homelinux.net>
On Tue, Jan 27, 2009 at 12:14, Sitaram Chamarty <sitaramc@gmail.com> 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.
next prev parent reply other threads:[~2009-01-30 5:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-27 17:14 gitk run from subdir and "find commit touching paths" Sitaram Chamarty
2009-01-30 5:56 ` Matt Graham [this message]
2009-01-30 13:39 ` Sitaram Chamarty
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=1c5969370901292156k2456b585r8e79889db516bc59@mail.gmail.com \
--to=mdg149@gmail.com \
--cc=git@vger.kernel.org \
--cc=sitaramc@gmail.com \
/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).