[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svn commit: r37806 - trunk/subversion/libsvn_repos

From: Neels Janosch Hofmeyr <neels_at_elego.de>
Date: Wed, 27 May 2009 03:17:56 +0200

Hyrum K. Wright wrote:
> On May 25, 2009, at 9:19 AM, Stefan Sperling wrote:
>
>> On Mon, May 25, 2009 at 08:08:17AM -0500, Hyrum K. Wright wrote:
>>> On May 24, 2009, at 3:55 PM, Neels Janosch Hofmeyr wrote:
>>>
>>>> Author: neels
>>>> Date: Sun May 24 13:55:35 2009
>>>> New Revision: 37806
>>>>
>>>> Log:
>>>> * subversion/libsvn_repos/reporter.c (drive):
>>> Move the function name to it's own line.
>> HACKING has examples like this:
>>
>> * dialects/nightingale.c (get_base_pitch): Allow 3/4-tone
>> pitch variation to account for trait variability amongst
>> isolated populations Erithacus megarhynchos.
>
> Oh, so it does.
>
> It's been a while since I've seen that format used, and we've seemed
> to standardize on the "separate line" format. Any objections to
> changing that example?
>
> -Hyrum

Well, if I have only one function name for a file, I remember having been
told to just write it out in one line. Makes sense to me...

* file.c (function): Rant.

* file2.c
  (function1): Rant.
  (function2): Rant.

But, blue, pink, I don't really care :)

~Neels

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2354754

Received on 2009-05-27 03:19:39 CEST

This is an archived mail posted to the Subversion Dev mailing list.