[geos-devel] Pending Commit: changes to single sided buffering & ogc validity checking

Andrew Ross grof at rogers.com
Mon Jul 19 17:07:02 EDT 2010


Does it make sense to include copyright notices for each change? If they
build up to the point people ignore them, if they aren't already ignoring
them ;-),  then it negates any value from having them there in the first

On 16 July 2010 15:39, strk <strk at keybit.net> wrote:

> On Fri, Jul 16, 2010 at 02:38:52PM -0400, Andrew Ross wrote:
> > Thanks for the explanation Paul. Very much appreciated.
> >
> > My apologies for prolonging this thread with one more question. In terms
> of
> > coding style, does it make sense to have the copyright notices for each
> > change in the code as this example? Should copyright notices from
> previous
> > modifications ever be removed? Please point me at the style guidelines if
> > this is already defined. Thanks again.
> There's no official style guidelines as far as I know
> (but could be wrong). What I try to do is follow the style
> I find in the file being edited.
> I started with TAB indenting for instance, but as others prefer
> spaces we're somewhere slowly moving there, for new code.
> You'll find a mix of TAB and spaces but hopefully only in different
> files.
> Changing the style of files has a bad effect on history tracking
> and regression debugging.
> About copyright, old notices shouldnt' be removed unless
> you're sure nothing is left from the original author.
> --strk;
>  ()   Free GIS & Flash consultant/developer
>  /\   http://strk.keybit.net/services.html
> _______________________________________________
> geos-devel mailing list
> geos-devel at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/geos-devel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/geos-devel/attachments/20100719/1ad03af6/attachment.html

More information about the geos-devel mailing list