--strict vs --no-newline
From: Julian Foad <julianfoad_at_btopenworld.com>
Date: Fri, 18 Jul 2014 19:06:04 +0100
Julian Foad wrote on 2014-06-17:
This is silly. Either we should add a 'no-newline' option for all of these (and conversely a 'newline' or 'add-newline' option for 'svnlook propget' because of its historically opposite default behaviour) or we should not add any such option just to one subcommand in v1.9. I added this option for 'youngest' recently because I assumed it was an anomaly that it didn't have the option, but it wasn't.
I'll revert the addition of the 'no-newline' option to 'svnlook youngest', if we don't come up with a better plan.
Then the 'no-newline' option to 'svn youngest' will also be an anomaly and I'll want to remove that too. But hopefully instead we'll agree to replace 'svn youngest' with some other UI (see mail thread "Don't release 'svn youngest'? [was: --strict vs --no-newline]").
>> Now I intend to:
Done in r1611698.
>> † * make 'svn propget --no-newline' an alias for 'svn propget --strict'.
No, let's not do that unless we offer 'no-newline' more widely than just in 'svn propget'. The existing 'strict' option (which means the same thing) is sufficient otherwise.
This is an archived mail posted to the Subversion Dev mailing list.