Notification mails for git repos

Derek Atkins warlord at MIT.EDU
Fri Feb 1 10:56:13 EST 2013

Geert Janssens <janssens-geert at> writes:

> Our current process (using the BP and AUDIT markers) has the same
> weaknesses IMO. There is no clear indication in the commit history of
> which commits were backported. We have BP/AUDIT as a visual reminder
> that backports should happen, but no easy way to check in retrospect
> if they actually happened.

Historically we had one developer whose job it was to backport fixes
into the stable release, effectively the "gatekeeper" for the stable
release.  This person's "job" was to audit every patch requested to
backport to stable and merge it in if it was safe.  When I had took this
role I just kept the 'audit' emails in my inbox until I processed them.
So I had a clear visual indicator of which changes I still had to look
at and process.

You are right that there is no visual history in the commit history; one
has to look at the commit log.  And you are right that there was no
in-the-SCM method to see if anything was missed.


       Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
       Member, MIT Student Information Processing Board  (SIPB)
       URL:    PP-ASEL-IA     N1NWH
       warlord at MIT.EDU                        PGP key available

More information about the gnucash-devel mailing list