Felipe Contreras <felipe.contreras@xxxxxxxxx> writes:
> On Thu, Feb 2, 2012 at 10:48 AM, Jonathan Nieder <jrnieder@xxxxxxxxx> wrote:
>
> Exactly, and "completion: avoid default value assignment on : true
> command" tells *nothing* to most people. Why is this patch needed? Do
> I care about it?
>
> OTOH "completion: be nicer with zsh" explains the purpose of the patch
> and people that don't care about zsh can happily ignore it if they
> want, and the ones that care about zsh might want to back port it, or
> whatever.
Perhaps you could compromise on
completion: work around zsh word splitting bug in : ${foo:=$(bar)}
?
> | tl;dr: $__git_porcelain_commands = $__git_all_commands
>
> Wrapping it up, to make clear what happens.
I think this is not good style for a commit message. Apart from the
very trendy use of tl;dr, it doesn't even properly summarize the cause
*or* the user-visible symptom. It just states how the confusion
propagates somewhere in the middle of the code.
--
Thomas Rast
trast@{inf,student}.ethz.ch
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html