I am a little confused by these commit messages. First, why are so many sent by dak180, even though he is not the committer? Second, I really really miss the ability to see the diff in trac with a link from the email. That was so helpful for a quick post-ex-facto code review. Since we do not have this link, it would be especially important to have a reference to the change's ticket. And to use the ticket system to allow code review before making changes.
Changes like the below trigger my uh-oh filter, but by the time I get back to my dev box, I will have forgotten about it. - Per On Wed, Oct 13, 2010 at 2:20 AM, dak180 <[email protected]> wrote: > This is an automated email from the git hooks/post-receive script. It was > generated because a ref change was pushed to the repository containing > the project "Warzone 2100 Project.". > > The branch, master has been updated > via 10f2bdede638766ed0ea198d750a00af95fbf110 (commit) > from 5923c455936febbf4303e80f22ac2c8ae431c6a1 (commit) > > Those revisions listed above that are new to this repository have > not appeared on any other notification email; so we list those > revisions in full, below. > > - Log ----------------------------------------------------------------- > commit 10f2bdede638766ed0ea198d750a00af95fbf110 > Author: Giel van Schijndel <[email protected]> > Date: Wed Oct 13 00:10:03 2010 +0200 > > scriptfuncs: store (possibly) signed values in signed variables > > Store map coordinates in a pair of signed integers as that's how > map_coord returns them. > > Signed-off-by: Giel van Schijndel <[email protected]> > > ----------------------------------------------------------------------- > > Summary of changes: > src/scriptfuncs.c | 6 +++--- > 1 files changed, 3 insertions(+), 3 deletions(-) > > > hooks/post-receive _______________________________________________ Warzone-dev mailing list [email protected] https://mail.gna.org/listinfo/warzone-dev
