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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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

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

--
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




[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]