Re: What's cooking in git.git (topics)

From: Junio C Hamano <gitster@pobox.com>
Date: Jul 20, 2008, 18:27 UTC
Message-ID: <7vd4l88l77.fsf@gitster.siamese.dyndns.org>
In-Reply-To: <20080720130407.GF10347@genesis.frugalware.org>

Miklos Vajna <vmiklos@frugalware.org> writes:

Show 5 quoted lines

> Third, it would be nice to allow passing extra parameter(s) to the
> backends, but I do not know what concept is the best here. The
> strategy1=foo,stategy2=bar limits the input to a single string. Is that
> enough? Given that recursive=theirs was considered harmful, we don't
> have too much examples;...

I personally think -sstrategy=string1,string2,... is simply a bad taste.

Why force yourself to parse things by having the users to concatenate something that the user could give us separated? If you care about the order and association between strategy and their options, you can always do:

	-s strategy1 -X option-1-for-strategy-1 -X option-2-for-strategy-1 \
	-s strategy2 -X option-1-for-strategy-2 ...