[geos-devel] Pending Commit: changes to single sided buffering &
ogc validity checking
pramsey at opengeo.org
Mon Jul 19 17:17:56 EDT 2010
This may be why PostgreSQL chooses to use the fictitious "PostgreSQL
Developers Group" for their copyright, however, I think we can cross
the bridge when we come to it. Doesn't seem to be slowing down Linux
On Mon, Jul 19, 2010 at 2:07 PM, Andrew Ross <grof at rogers.com> wrote:
> 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
>> 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.
>> () Free GIS & Flash consultant/developer
>> /\ http://strk.keybit.net/services.html
>> geos-devel mailing list
>> geos-devel at lists.osgeo.org
> geos-devel mailing list
> geos-devel at lists.osgeo.org
More information about the geos-devel