[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Google
  Web www.spinics.net

Re: What is going on with GPM sources/copyright?



On Sunday 02 May 2010 03:27:28 pm Enrico Weigelt wrote:
> * Dmitry Torokhov <dmitry.torokhov@xxxxxxxxx> wrote:
> > Is it some uber cool programming technique that requires splitting
> > _every_ function into a separate source file?
> 
> Maintenability ?
> Lesser change of conflicts on merge / rebase ?
> Faster incremental rebuilds ?

*sigh* No, not really. Unless you produce 20 KLOC monsters the compile
time benefit either non-existent or you may even hurt from having to
re-parse include files more than before. But you are certainly loose
in cases when some parts of the code can be inlined and/or eliminated
- compiler can't make this decision when you split everything apart and
everything is extern.

There is a reason why function != module.

> 
> > More importantly, why copyright notices of all former contributors have
> > been stripped off once the code was moved? It is one thing to add your
> > own copyright string (although even that requires the change to be
> > copyrightable and not a mechanical transformation) but claiming sole
> > copyright over entire body of code it something quite different.
> 
> Why not just having it all in one AUTHORS file ?
>

A person may have copyright interest in just a part of the project,
not the whole thing. 
 
> If someone's interested in an in-depth analysis - `git log`
> might help ...

The most significant contributions predate git by about 10 years. The
history is simply isn't there. And event if it was, copyright is not
to be stripped from the work.

-- 
Dmitry
_______________________________________________
gpm mailing list
gpm@xxxxxxxxxxxxxx
http://lists.linux.it/listinfo/gpm

[Kernel Development]     [Red Hat Install]     [Red Hat Watch]     [Red Hat Development]     [Gimp]     [Yosemite News]

Powered by Linux