Re: --no-newline vs. --strict

Branko Čibej <brane_at_wandisco.com> writes:

> The single usage of the --strict option is arguably complete nonsense:
> the default docstring, which isn't displayed *anywhere*, is 'use strict
> semantics' and ... means nothing at all. In actual usage, --strict is
> hardly mnemonic for not printing trailing newlines.

--strict originally did more. r845498, in 1.0, shows that --strict
originally stripped both the the path prefix and the newline. r872554,
in 1.6, limited --strict to a single path at which point it just
stripped newlines.

> Given all that, I propose we deprecate --strict and conflate the actual
> option value with --no-newline, like this (this is trunk, untested):

That looks like a good solution.

-- 
Philip Martin | Subversion Committer
WANdisco // *Non-Stop Data*