[vhffs-dev] [GIT] vhffs4/vhffs.git branch master updated. bbaa28bd7ae21cd4b7023381c2c92b4129f8f059 |
[ Thread Index |
Date Index
| More vhffs.org/vhffs-dev Archives
]
- To: vhffs-dev@xxxxxxxxx
- Subject: [vhffs-dev] [GIT] vhffs4/vhffs.git branch master updated. bbaa28bd7ae21cd4b7023381c2c92b4129f8f059
- From: git@xxxxxxxxxxxxx
- Date: Sun, 04 Sep 2016 20:33:00 +0200
- Auto-submitted: auto-generated
This is an automated email from git. It was generated because a ref
change was pushed to the "vhffs4/vhffs.git" repository.
The branch, master has been updated
via bbaa28bd7ae21cd4b7023381c2c92b4129f8f059 (commit)
from f61974a3f2b36e7d60bc49ad2c41666b3fd67d68 (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 bbaa28bd7ae21cd4b7023381c2c92b4129f8f059
Author: Sylvain Rochet <gradator@xxxxxxxxxxxx>
Date: Sun Sep 4 18:27:11 2016 +0000
svn, git, mercurial, bazaar: fix uninitialized value $mladdress in pattern match
Commit cb6df60289 ("Add option to have a default destination for
commit mails") introduced a regression in which database value for
ml_name column can be NULL if notify_default config value is unset
instead of the previously used '' hardwired default.
Unfortunately robots didn't check for this condition. Instead of
re-introducing the default to '', fix the robots to properly handle the
case, since having a NULL value in database for an unset value is
perfectly acceptable.
-----------------------------------------------------------------------
Summary of changes:
vhffs-api/src/Vhffs/Robots/Bazaar.pm | 5 +++--
vhffs-api/src/Vhffs/Robots/Git.pm | 8 ++++----
vhffs-api/src/Vhffs/Robots/Mercurial.pm | 7 +++----
vhffs-api/src/Vhffs/Robots/Svn.pm | 10 +++++-----
4 files changed, 15 insertions(+), 15 deletions(-)
hooks/post-receive
--
vhffs4/vhffs.git