[47] in athena10
Athena repository ground rules
daemon@ATHENA.MIT.EDU (Greg Hudson)
Tue Jan 15 04:09:44 2008
Date: Tue, 15 Jan 2008 04:09:32 -0500
Message-Id: <200801150909.m0F99WDF022708@equal-rites.mit.edu>
From: Greg Hudson <ghudson@MIT.EDU>
To: athena10@MIT.EDU
Here are the basic rules I'd like us to follow for the Athena 10
repository:
1. We'll use post-commit review, which is to say we won't be using the
source-reviewers mailing list for Athena 10 development (we will
continue to use it for 9.4 stuff going into the CVS repository).
Instead, people should watch for svn commits to the source-commits
list and, time permitting, review them. If the commit adds a file,
I believe the mail message won't include the new file contents,
you'll have to "svn diff -c REVNUM svn+ssh://svn.mit.edu/athena"
(or file://afs/dev.mit.edu/source/svn-repos if you're not a
commiter) to review the full commit.
2. tabbott and andersk should feel free to modify any part of trunk
that they understand well enough to touch, including the stuff
under athena/. For example, to render a patch to an Athena
directory unneeded by applying it to the base sources if it's a
simple fix. If what you do runs counter to my written or unwritten
plans, I'll raise a flag here and we'll discuss it.
3. Please use the following approximate style of commit log messages,
which is loosely derived from the Gnu changelog format:
---
General summary of the commit; can be omitted if it's a commit to one
file or otherwise obvious from the per-file changes.
* path/to/file1: Change to a non-structured file.
* path/to/file2 (symbol): Simple change to a structured file like C
source code.
* path/to/file2
(symbol1): Change to a symbol within a file.
(symbol2, symbol3): Similar change made to multiple symbols within a
file.
---
This is a convention derived from the Subversion project and it's
a bit of work, but I find it useful. If your commit includes the
addition of a debian/changelog entry, you do not need to note that
in the Subversion commit log message; that would be silly. Do not
include "trunk" in the pathnames. There are plenty of examples in
recent commits I've made to the project.
