5 ms·
Why in the Release Notes do they use the verb "learned" to describe adding a command line option to a feature? "git cherry-pick" learned the "--allow-empty-m
by Osiris 14y ago
Why in the Release Notes do they use the verb "learned" to describe adding a command line option to a feature?
"git cherry-pick" learned the "--allow-empty-message" option
It's not like Git has obtained sentience and has started to teach itself new tricks, though that would be an interesting development.
I understand what they are trying to say I just thought the choice of verb and subject was odd, leaving out the developers as those acting on the code.
- derleth 14y agoDevelopers often anthropomorphize things to gloss over irrelevant details. The focus is on what, not how, and anthropomorphizing is the quickest route to get that across.
- peff 14y agoWriting it in the passive voice is slightly more awkward. E.g., "git cherry-pick" was enhanced with an "--allow-empty-message option". Similarly, writing it in the active voice but attributing the verb properly ends up with meaningless words: "Developers taught cherry-pick to..." or "We taught cherry-pick to...". Every entry would begin that way; having the first words be the relevant subsection of git makes it easier to skim through the release notes.
- malkarouri 14y agoI would have gone for "git cherry-pick" acquired the "--allow-empty-message" option or "git cherry-pick" now has the "--allow-empty-message" option myself. I think the subject is fine with the emphasis where it belongs. The verb is weird, though.