On 11/16/2016 03:42 PM, Kevin Bullock wrote:
On Nov 10, 2016, at 09:47, Pierre-Yves David <pierre-yves.da...@ens-lyon.org>
wrote:
On 11/08/2016 04:07 PM, Augie Fackler wrote:
I'm -0 on the word "troubles": it feels wrong in a way I'm having
trouble describing. It definitely feels odd to have a plural for the
label (the line for tags is "tag:" after all) - maybe "trouble:" would
be better?
Apparently the usage is to use singular even when there might be multiples (eg: bookmark,
tag) so we should me to "trouble:"
(I'm very open to better word choices here than trouble, but I have
none to offer.)
As for the word "trouble", people have been voicing concern for about 5 years without significant
counter-proposal, so I'm moving forward with that word. For my part, I'm not a native speaker and
"trouble" works fine for me, exchanging mutable changeset can lead to some
"unavoidable/intrinsic troubles".
Because anyway, Evolution is still an experimental feature and is therefor still subject
to possible wording and feature changes. So this "trouble:" line could change
in the future if someone eventually make progress here
I'm also not keen on 'troubles'. For this purpose, I'd suggest 'evolution:' by analogy to
'bisect:'. That won't work for referring to the combined set of {divergences, bumps,
...}, but for labelling "this changeset's evolution status" I think it works.
'Evolution' is an interesting proposal. It could be nice as generic
terms in multiple place. However, we still need a proper terms to refer
to "trouble" in the documentation/etc…. I do not feel like "evolution
status" is appropriate. I do not see "status" appropriate for "a 0-n
list of things" and, to me, it also fails to carry out the fact
"trouble" are problems that needs to get fixed.
Cheers,
--
Pierre-Yves David
_______________________________________________
Mercurial-devel mailing list
Mercurial-devel@mercurial-scm.org
https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel