git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [TIG RFC] Cleaning up tig's option handling

From
Greg KH <greg@kroah.com>
Date
Feb 7, 2008, 06:30 UTC
Message-ID
<20080207063048.GA22148@kroah.com>
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
Previous: Jonas Fonseca
Message 2 of 2 in “[TIG RFC] Cleaning up tig's option handling”
  1. Jonas FonsecaFeb 6, 2008
  2. Greg KHFeb 7, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.