Update of bug #5994 (project savane):
Status: None => In Progress
_______________________________________________________
Follow-up Comment #1:
> In sv_aliases.pl, I added a call to PrintGroupAliasesList(),
> which is a function I added to Groups.pm. This function adds
> aliases to the /etc/mail/aliases file for each project group,
> where the group name is the alias for all the member emails.
Beware that Savane allow a project and a user to have the same name. You can
get conflicts.
> In Cvs.pm, I modified the CvsMakeArea() function to do 2
> things:
> 1) symlink to $dir_cvs/../OMMON-SCRIPTS/log
> 2) append a line to the project's cvs loginfo file for using
> the 'log' script.
I think we can come with a more flexible approach. For example, users want to
specify diff options, whether they want diffs, and if yes as separate mails or
not, whether all users should get notifications or only a given mailing list,
etc.
Here's my log_accum config:
In commitinfo:
DEFAULT /usr/local/bin/commit_prep.pl -T testyeight_1 %p
In loginfo:
DEFAULT echo "Sending mail notification..."; /usr/local/bin/log_accum.pl -m
[EMAIL PROTECTED] -d -T testyeight_1 -c /etc/log_accum-sources.config %p %{sVv}
In /etc/log_accum-sources.config:
cvsweb http://cvs.savannah.gnu.org/viewcvs
I updated my script for the new log_accum syntax:
http://arch.savannah.gnu.org/head/administration/infra/main/0/cvs/generate_log_accum.pl
Now it's only a matter of grabbing the info out of the database.
Can you take care of this while I work on the frontend part?
_______________________________________________________
Reply to this item at:
<http://gna.org/bugs/?func=detailitem&item_id=5994>
_______________________________________________
Message posté via/par Gna!
http://gna.org/
_______________________________________________
Savane-dev mailing list
[email protected]
https://mail.gna.org/listinfo/savane-dev
