kfogel@tigris.org writes:
> Log:
> Change wording to indicate that we're following the GNU coding
> standards only "loosely". :-)
That wasn't an accurate log message (I've since changed it).
Basically, just made a note saying do left parens any old way you
please. :-)
-K
> See dev messages from Greg Stein, Greg Hudson, and myself on this
> (<20010212183750.V8123@lyra.org>,
> <200102131635.LAA05760@egyptian-gods.MIT.EDU>, and
> <87g0hizr40.fsf@galois.ch.collab.net>).
>
> Revision Changes Path
> 1.24 +7 -1 subversion/HACKING
>
> Index: HACKING
> ===================================================================
> RCS file: /cvs/subversion/HACKING,v
> retrieving revision 1.23
> retrieving revision 1.24
> diff -u -r1.23 -r1.24
> --- HACKING 2001/02/01 12:24:26 1.23
> +++ HACKING 2001/02/13 17:09:28 1.24
> @@ -7,7 +7,7 @@
> HACKER'S GUIDE TO SUBVERSION
> ============================
>
> - Last updated: $Date: 2001/02/01 12:24:26 $
> + Last updated: $Date: 2001/02/13 17:09:28 $
>
>
> TABLE OF CONTENTS
> @@ -185,6 +185,12 @@
> avoid "code crunch". Don't worry too much about vertical density;
> it's more important to make code readable than to fit that extra line
> on the screen.
> +
> +The controversial GNU convention of putting a space between a function
> +name and its opening paren is optional in Subversion. If you're
> +editing an area of code that already seems to have a consistent
> +preference about this, then just stick with that; otherwise, pick
> +whichever way you like.
>
>
>
>
>
>
Received on Sat Oct 21 14:36:22 2006