What do you all think about developer's email in source code? Is there a need for it at all there?
WBR, Aleksey.
On Jan 10, 2010, at 1:43 AM, ekohl@svn.reactos.org wrote:
Author: ekohl Date: Sat Jan 9 23:43:16 2010 New Revision: 45020
URL: http://svn.reactos.org/svn/reactos?rev=45020&view=rev Log: Removed outdated email addresses. Modified: trunk/reactos/ntoskrnl/ke/queue.c URL: http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/ke/ queue.c?rev=45020&r1=45019&r2=45020&view=diff ====================================================================== ======== --- trunk/reactos/ntoskrnl/ke/queue.c [iso-8859-1] (original) +++ trunk/reactos/ntoskrnl/ke/queue.c [iso-8859-1] Sat Jan 9 23:43:16 2010 @@ -5,7 +5,7 @@
- PURPOSE: Implements kernel queues
- PROGRAMMERS: Alex Ionescu (alex.ionescu@reactos.org)
Gunnar Dalsnes
Eric Kohl (ekohl@rz-online.de)
*/
Eric Kohl
Hello Aleksey. Would be useful to reach the developers if anybody wants to ask about the code, or ReactOS, or their development in general.
On Sun, Jan 10, 2010 at 12:43 PM, Aleksey Bragin aleksey@reactos.orgwrote:
What do you all think about developer's email in source code? Is there a need for it at all there?
WBR, Aleksey.
On Jan 10, 2010, at 1:43 AM, ekohl@svn.reactos.org wrote:
Author: ekohl Date: Sat Jan 9 23:43:16 2010 New Revision: 45020
URL: http://svn.reactos.org/svn/reactos?rev=45020&view=rev Log: Removed outdated email addresses. Modified: trunk/reactos/ntoskrnl/ke/queue.c URL: http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/ke/ queue.c?rev=45020&r1=45019&r2=45020&view=diff ====================================================================== ======== --- trunk/reactos/ntoskrnl/ke/queue.c [iso-8859-1] (original) +++ trunk/reactos/ntoskrnl/ke/queue.c [iso-8859-1] Sat Jan 9 23:43:16 2010 @@ -5,7 +5,7 @@
- PURPOSE: Implements kernel queues
- PROGRAMMERS: Alex Ionescu (alex.ionescu@reactos.org)
Gunnar Dalsnes
Eric Kohl (ekohl@rz-online.de)
*/
Eric Kohl
Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
I guess we could even live without the developer names in the file header. Just inserting "ReactOS dev team" or similar would save a lot of useless discussions. Current name listings are normally incomplete anyways and only a SVN blame can reveal the real authors. For credits and E-Mail contacts there's a credits file.
2010/1/10 Alwyn Tan alwyn.tan@gmail.com
Hello Aleksey. Would be useful to reach the developers if anybody wants to ask about the code, or ReactOS, or their development in general.
On Sun, Jan 10, 2010 at 12:43 PM, Aleksey Bragin aleksey@reactos.orgwrote:
What do you all think about developer's email in source code? Is there a need for it at all there?
WBR, Aleksey.
On Jan 10, 2010, at 1:43 AM, ekohl@svn.reactos.org wrote:
Author: ekohl Date: Sat Jan 9 23:43:16 2010 New Revision: 45020
URL: http://svn.reactos.org/svn/reactos?rev=45020&view=rev Log: Removed outdated email addresses. Modified: trunk/reactos/ntoskrnl/ke/queue.c URL: http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/ke/ queue.c?rev=45020&r1=45019&r2=45020&view=diff ====================================================================== ======== --- trunk/reactos/ntoskrnl/ke/queue.c [iso-8859-1] (original) +++ trunk/reactos/ntoskrnl/ke/queue.c [iso-8859-1] Sat Jan 9 23:43:16 2010 @@ -5,7 +5,7 @@
- PURPOSE: Implements kernel queues
- PROGRAMMERS: Alex Ionescu (alex.ionescu@reactos.org)
Gunnar Dalsnes
Eric Kohl (ekohl@rz-online.de)
*/
Eric Kohl
Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
On Sun, Jan 10, 2010 at 3:56 PM, Gregor Schneider grschneider@gmail.com wrote:
I guess we could even live without the developer names in the file header. Just inserting "ReactOS dev team" or similar would save a lot of useless discussions. Current name listings are normally incomplete anyways and only a SVN blame can reveal the real authors. For credits and E-Mail contacts there's a credits file.
It is the authors job to insure his name appears in the header if he is contribution enough to a source file to have a copyright claim.