Progress terminology

[Martin Geisler]

Greg Ward <greg-hg at gerg.ca> writes:

> On Thu, Mar 11, 2010 at 1:43 PM, Benoit Boissinot <bboissin at gmail.com> wrote:
>> Please devise a best-practice for progress keywords, I'm usually
>> struggling to find good words.
>
> As one of the self-appointed English grammar goons, may I suggest the
> present participle of a common verb? E.g. "bundling", "searching",
> "cloning", "adding", etc.

I agree, I'll change the strings to that form. Thanks for the
suggestion.

> In the case of churn, there's not an obvious choice.  "Processing" and
> "analyzing" both seem reasonable to me.  "Churning" is NOT the right
> choice, since churning is what programmers do to a codebase as they
> add changesets to it.  The 'churn' extension analyzes code churn.

I like "analyzing" a lot, so I'll change it to that.

> (The original meaning of "to churn" is what you do to cream to turn it
> into butter, ie. it changes the state of a system. If the churn
> extension actually turned my cream repo into butter, I'd be quite
> surprised.)

Heh, I think many people would be surpriced to see that happen :-)

-- 
Martin Geisler

Fast and powerful revision control: http://mercurial.selenic.com/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://selenic.com/pipermail/mercurial-devel/attachments/20100315/c810099f/attachment.pgp>