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

Re: git-subtree: directory mismatch

From: Björn Steinbrink <hidden>
Date: 2016-06-15 22:47:46

On 2009.11.25 18:20:45 -0500, Avery Pennarun wrote:
On Wed, Nov 25, 2009 at 6:17 PM, Johannes Schindelin
[off-list ref] wrote:
quoted
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?
I guess it's -Xfoo vs. -X foo (note the space). Same deal with log
-S<string>. "git log -S foo" would look for an empty string (I guess)
being added/removed in some commit in foo's history, while "git log
-Sfoo" looks for "foo" being added/remove in HEAD's history.

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