Ben noticed a usage message that could be improved, and is about to
commit the new version to trunk.
It was never totally clear whether this kind of tweak is included in
"Doc fixes in core code header or source files", which can be merged
to 1.0 without restarting the soak time, as long as they're approved
by voting. Let's resolve that ambiguity by explicitly allowing them
-- I mean, big deal, a usage message changed :-), that's no reason to
restart the soak. Our procedures are meant to help us avoid real
risk, but beyond that shouldn't get in the way of improvements.
So, would anyone object to this change to HACKING?
Index: HACKING
===================================================================
--- HACKING (revision 8560)
+++ HACKING (working copy)
@@ -1512,6 +1512,8 @@
With voting:
- Anything affecting only tools/, packages/, or bindings/.
- Doc fixes in core code header or source files.
+ - Changes to printed output, such as error and usage messages, as
+ long as format string "%" codes and their args are not touched.
Core code changes, of course, require voting, and restart the soak or
test period, since otherwise the change could be undertested.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Feb 5 17:46:36 2004