river-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Calum Shaw-Mackay" <calum.shawmac...@gmail.com>
Subject Re: thoughts on River project organization...
Date Mon, 05 Feb 2007 16:13:02 GMT
Hi all

'First time caller, long time listener......' :)

You can try to enforce code styles such as indentation through
pre-commit hooks in subversion, but this is generally frowned upon, as
ther's no way of getting the reformeted code back to the commiter and
forcing the file to refresh (aka commit and update in the same

As an aside this could be used for checking for the appropriate
preamble at the top of the file.

Does anyone know if there is a way of moderating commited files for
approval, and as part of this approval, handle the formatting

I think the best thing may be get everyone to be fairly happy with the
style, and if someone varies wildly from it, and frown at them evilly



On 05/02/07, Gregg Wonderly <gergg@cox.net> wrote:
> Mark Brouwer wrote:
> > Jeff Ramsdale wrote:
> >
> >> Similarly, 80 column line length is just goofy given screen
> >> real-estate these days. I prefer 120. It's time to update the
> >> "standards." That said, I'll go with the group consensus. :-)
> >
> >
> > Go wash your mouth Jeff, anybody that performs three-way merges on a
> > regular basis will tell you 80 column width still rulezzzzz.
> When I'm doing three way merges, I reformat the affected lines as needed to make
> sense of what is there.  Typically though, I don't have too many three way
> merges because we try hard to keep multiple people from working in the same
> areas of files.
> When you have to do it though, there are certainly many characteristics of the
> file which create issues for making the merge go fast and correctly.
> Gregg Wonderly

View raw message