Re: vino branched
- From: James Henstridge <james jamesh id au>
- To: Jeff Waugh <jdub perkypants org>
- Cc: GNOME I18N List <gnome-i18n gnome org>, GNOME Hackers <gnome-hackers gnome org>, desktop-devel-list gnome org
- Subject: Re: vino branched
- Date: Thu, 19 May 2005 23:35:28 +0800
Jeff Waugh wrote:
><quote who="Luis Villa">
>
>
>
>>Someone with more perl-fu than me- would it be possible to set up a script
>>to watch cvs-commits list and send this kind of mail out automatically, or
>>just update a webpage somewhere? Making maintainers do this manually (and
>>remember to do it automatically) seems sort of crap...
>>
>>
>
>Unless you set up a polling mechanism for branches that exist on particular
>important files, you'd never know - there's no hook mechanism for branching
>that I know of (and certainly not related to commit).
>
>
There is the CVSROOT/taginfo file, which says what to do when some files
are tagged (similar to how CVSROOT/loginfo lists programs to run on
commits).
I don't know if there are any existing taginfo scripts that could easily
be used for what Luis suggested though.
James.
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]