Thread (5 messages) flat view 5 messages, 4 authors, 2016-06-15

Re: git-subtree: directory mismatch

From: Avery Pennarun <hidden>
Date: 2016-06-15 22:47:46

On Wed, Nov 25, 2009 at 6:17 PM, Johannes Schindelin
[off-list ref] wrote:
On Wed, 25 Nov 2009, Junio C Hamano wrote:
quoted
I do remember some people didn't like -X<option> syntax but I don't
think there was any solid counterproposal to achieve a similar goal to
satisfy the need to pass arbitrary parameters to the merge strategy
backends.
I took exception to the awkward way to specify the option.  A strong hint
just how awkward -X<option> is: it is hard to implement using
parse-options.
I read the earlier thread and I still don't quite understand this
point.  What makes it difficult?  X seems just like any other option
that takes a string parameter (which is easily supported by getopt at
least; I haven't played with parse_options but I certainly hope it's
as good as getopt).

The string parameter (say, $x) is translated directly into "--$x" and
passed as exactly one argument of the argv array to the subprogram.
Easy, right?  Plus Junio already wrote a patch to do it (which I'm in
the process of forward-porting) and it seems pretty straightforward.

Perhaps I'm missing something.

Thanks,

Avery
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help