From: Greg KH <greg@kroah.com>
To: Jonas Fonseca <fonseca@diku.dk>
Cc: git@vger.kernel.org
Subject: Re: [TIG RFC] Cleaning up tig's option handling
Date: Wed, 6 Feb 2008 22:30:48 -0800 [thread overview]
Message-ID: <20080207063048.GA22148@kroah.com> (raw)
In-Reply-To: <20080206235734.GA9969@diku.dk>
On Thu, Feb 07, 2008 at 12:57:34AM +0100, Jonas Fonseca wrote:
> Hello,
>
> In my own usage of tig, I increasingly use git-log options like -S and
> --all and rarely use any of the "native" tig options or subcommands.
Same for my usage, and I use tig a lot too.
> I would like to ask tig users out there on how to best proceed with
> cleaning up the option handling so that tig will act more like gitk.
Anything that works more like gitk would be fine with me, no objection
to changing the options at all.
thanks,
greg k-h
prev parent reply other threads:[~2008-02-07 6:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-06 23:57 [TIG RFC] Cleaning up tig's option handling Jonas Fonseca
2008-02-07 6:30 ` Greg KH [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=20080207063048.GA22148@kroah.com \
--to=greg@kroah.com \
--cc=fonseca@diku.dk \
--cc=git@vger.kernel.org \
/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