From: Jakub Narebski <jnareb@gmail.com>
To: Jeff King <peff@peff.net>
Cc: Avery Pennarun <apenwarr@gmail.com>,
Sverre Rabbelier <srabbelier@gmail.com>,
Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org
Subject: Re: rfc - Changing the way gitk and git-gui are managed
Date: Tue, 27 Jul 2010 03:28:17 -0700 (PDT) [thread overview]
Message-ID: <m3k4ohkyns.fsf@localhost.localdomain> (raw)
In-Reply-To: <20100727053040.GA6014@coredump.intra.peff.net>
Jeff King <peff@peff.net> writes:
> On Fri, Jul 23, 2010 at 02:16:45AM -0400, Avery Pennarun wrote:
>
> > Only this: Junio said that there are no major downsides to this change
> > - and given the slow pace of change in gitk/git-gui, this is probably
> > true - but are there any *upsides*? What problem does this solve?
>
> One minor complaint with the current setup is that browsing the history
> with path limiting is unintuitive. You can't do "gitk gitk" in the
> gitk-git directory. You must instead do "cd .. && gitk -- gitk".
Do 'gitk --relative=gitk' or 'gitk --relative' work?
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2010-07-27 10:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-23 2:39 rfc - Changing the way gitk and git-gui are managed Junio C Hamano
2010-07-23 4:04 ` Sverre Rabbelier
2010-07-23 6:16 ` Avery Pennarun
2010-07-27 5:30 ` Jeff King
2010-07-27 5:42 ` Avery Pennarun
2010-07-27 5:46 ` Jeff King
2010-07-27 10:28 ` Jakub Narebski [this message]
2010-07-23 6:54 ` Will Palmer
2010-07-25 10:44 ` Sam Vilain
2010-07-23 19:18 ` Greg Troxel
2010-07-24 11:02 ` Nicolas Sebrecht
2010-07-24 12:54 ` Jonathan Nieder
2010-07-24 12:57 ` Jonathan Nieder
2010-07-24 14:00 ` Nicolas Sebrecht
2010-07-24 17:22 ` Jonathan Nieder
2010-07-24 19:18 ` Avery Pennarun
2010-07-24 19:34 ` Jonathan Nieder
2010-07-25 4:11 ` Avery Pennarun
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=m3k4ohkyns.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=apenwarr@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
--cc=srabbelier@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.