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

Re: [PATCH] [RFC] Add a new config. option for skipping merges in git-log

From
KKKoosha Khajehmoogahi <koosha@posteo.de>
Date
Mar 16, 2015, 20:59 UTC
Message-ID
<55074440.90709@posteo.de>
In-Reply-To
<xmqqy4mwpsyn.fsf@gitster.dls.corp.google.com>
On 03/16/2015 09:50 PM, Junio C Hamano wrote:
Show 7 quoted lines
> The command line overrides the config, no?  If you set up what the
> command line defaults to from the config, let the command line
> parser do whatever it wants to do, and do nothing else after the
> command line parser returns, wouldn't that be sufficient?
> 
> Puzzled...
>

Yes, the command line overrides the config. But, the config and command line parameters are parsed in two different files. The question is how you would read the config in revision.c while parsing the command line when there is no function in revision.c for that?

Sorry if I look baffled.
-- 
Koosha
Previous: Junio C HamanoNext: Junio C Hamano
Message 7 of 8 in “[RFC] Add a new config. option for skipping merges in git-log”
  1. [RFC] Add a new config. option for skipping merges in git-logKoosha Khajehmoogahi, Mar 16, 2015
  2. [RFC] Add a new config. option for skipping merges in git-logKoosha Khajehmoogahi, Mar 16, 2015
  3. [RFC] Add a new config. option for skipping merges in git-logKoosha Khajehmoogahi, Mar 16, 2015
  4. Junio C HamanoMar 16, 2015
  5. Koosha KhajehmoogahiMar 16, 2015
  6. Junio C HamanoMar 16, 2015
  7. Koosha KhajehmoogahiMar 16, 2015
  8. Junio C HamanoMar 16, 2015

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.