[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Muddleftpd-cvs] muddleftpd Developer.txt
From: |
Joerg Jaspert |
Subject: |
[Muddleftpd-cvs] muddleftpd Developer.txt |
Date: |
Sun, 20 Oct 2002 11:03:04 -0400 |
CVSROOT: /cvsroot/muddleftpd
Module name: muddleftpd
Changes by: Joerg Jaspert <address@hidden> 02/10/20 11:03:04
Modified files:
. : Developer.txt
Log message:
Added Section about Changelogs/Commit Messages.
Changed (C) for new Files to be for the Muddleftpd team.
CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/muddleftpd/muddleftpd/Developer.txt.diff?tr1=1.2&tr2=1.3&r1=text&r2=text
Patches:
Index: muddleftpd/Developer.txt
diff -c muddleftpd/Developer.txt:1.2 muddleftpd/Developer.txt:1.3
*** muddleftpd/Developer.txt:1.2 Sun Oct 20 06:35:22 2002
--- muddleftpd/Developer.txt Sun Oct 20 11:03:04 2002
***************
*** 1,5 ****
--- 1,7 ----
Muddleftpd Developer Guidelines
+ This is: $Revision: 1.3 $.
+
[Note before: That text is assembled from different other guidelines I
read and some talks I had with other people.]
***************
*** 10,17 ****
1.2 CVS Branches
1.3 Muddleftpd Releases
1.4 Security Updates, Important Bugfixes
! 1.5 Code Submission if you are not a developer of Muddleftpd
! 1.6 How to become a developer
1.0 Copyright issues
--- 12,20 ----
1.2 CVS Branches
1.3 Muddleftpd Releases
1.4 Security Updates, Important Bugfixes
! 1.5 ChangeLog Entries and CVS commit messages (log messages)
! 1.6 Code Submission if you are not a developer of Muddleftpd
! 1.7 How to become a developer
1.0 Copyright issues
***************
*** 22,28 ****
/* FILENAME SHORT DESCRIPTION OF THE FILE
! Copyright (C) 1999 Beau Kuiper
This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
--- 25,31 ----
/* FILENAME SHORT DESCRIPTION OF THE FILE
! Copyright (C) 2002 Muddleftpd Team, http://www.nongnu.org/muddleftpd/
This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
***************
*** 187,195 ****
finished yet (hey, we aim to produce a secure ftp daemon, that needs
time) but still can react quickly on such bugs.
! 1.5 Code Submission if you are not a developer of Muddleftpd
When you fix a bug or add a feature, you must submit a unified patch
(see below for instructions for creating the patch) to the Patch Manager
--- 190,219 ----
finished yet (hey, we aim to produce a secure ftp daemon, that needs
time) but still can react quickly on such bugs.
+
+ 1.5 ChangeLog Entries and CVS commit messages (log messages)
+
+ First please take a look at the following URL. The text there is really
+ good, you should follow it as close as possible:
+ http://www.red-bean.com/cvs2cl/changelogs.html
+
+ We require that you follow these guidelines while creating your
+ ChangeLog entry. Reasons are listed there too, mainly to have a clear
+ log of changes that are done to the source.
+
+ Talking about messages for cvs commit:
+ You can just re-use the logmessage from the ChangeLog for the commit
+ message (Emacs CVS Mode does it for you if you use that), thats fine.
+ But if you write them by Hand it is enough if you write a clear
+ sentence (or many of them) describing your changes to the file(s) you
+ commit. For details everyone could look into the ChangeLog. But NEVER
+ commit with an empty Message or just a "changed". That way everyone can
+ follow the changes you made with the cvs log output and can look into
+ the ChangeLog file for a detailed description of the changes.
+
! 1.6 Code Submission if you are not a developer of Muddleftpd
When you fix a bug or add a feature, you must submit a unified patch
(see below for instructions for creating the patch) to the Patch Manager
***************
*** 227,233 ****
configure scripts.
! 1.6 How to become a developer
Well, thats not that hard. Of course we require a little knowledge, so
you have to prove you can do the work you say you want to do.
--- 251,257 ----
configure scripts.
! 1.7 How to become a developer
Well, thats not that hard. Of course we require a little knowledge, so
you have to prove you can do the work you say you want to do.