Re: [PATCH 1/1] change contract between system_path and it's callers

From: Philip Oakley <philipoakley@iee.org>
Date: Nov 28, 2014, 11:13 UTC
Message-ID: <7FDD11B6900A41269F60C9E60A11D84C@PhilipOakley>
In-Reply-To: <CANCZXo63q2YmTcYr9Vf99fAAnENNj7vE1nC18QJDYve=-OcXyQ@mail.gmail.com>

From: "Alexander Kuleshov" <kuleshovmail@gmail.com>
Sent: Wednesday, November 26, 2014 3:53 AM

Show 7 quoted lines

>>
>> None of these warrant the code churn, I would say.
>
> Sorry, english is not my first language, what did you mean when
> saying:
> "code churn"? Code duplication or something else?
> --

Hi Alexander,

The term 'churn' is originally from British butter making.

Churn:
verb
  1.shake (milk or cream) in a machine in order to produce butter.
  "the cream is ripened before it is churned"
        synonyms: stir, agitate;

   2.(with reference to liquid) move or cause to move about vigorously.
  "the seas churned".

For Code (used in a somewhat negative sense), it means that lots of bits are moved around a great deal for little apparent benefit.

In the sense Junio used it, I believe it's suggesting that the balance between the amount of change and usefulness of the change had gone further than hoped. (Though Junio is usually open to receiving a well argued case)

Philip see also http://en.wikipedia.org/wiki/Churn_rate