Re: Recent unresolved issues

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Apr 15, 2006, 11:46 UTC
Message-ID: <Pine.LNX.4.63.0604151343010.25269@wbgn013.biozentrum.uni-wuerzburg.de>
In-Reply-To: <7vk69ri5cp.fsf@assigned-by-dhcp.cox.net>

Hi,

On Sat, 15 Apr 2006, Junio C Hamano wrote:

> Honestly, the longer I look at it, the more I feel that this way
> might break more things than it fixes.  I haven't even looked at
> blame.c or http-push.c to see what's broken yet.

I do not have time to look at this closely, but it sounds to me like you need a two-stage approach:

setup_diff_options(&options); [... set defaults ...] handle_cmdline_arguments(&options); [... possibly check if the user overrode some defaults ...]

I think that the unified option parsing is the right approach.

Ciao, Dscho

$ 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.