[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Lots of pkgdb mail on commits list

Hash: SHA1

Michael Schwendt wrote:
> On Thu, 30 Aug 2007 14:20:20 +0200, Michael Schwendt wrote:
>>> It's topic: "All cvs commits"
>> Is anybody else also missing some commit messages?
>> I'm subscribed to
>> [X] 	Replies (Details)
>> [X]	All cvs commits (Details)
>> but what arrives here seems to be incomplete.
> Perhaps a catch-all regexp at the bottom of the topic list is not
> possible? As in "if an earlier regexp in the list matches but user is not
> subscribed to the topic, the mail is thrown away and the rest of the
> regexp list is not evaluated".
> As a test I've now subscribed also to "Package commits" which comes
> earlier in the list.
That would have been my thought as well except that I had tested that
when I first started creating the topics.

I think I've fixed it now although there's something I'm not
understanding about the flavour of regular expression our mailman
instance is using.

The difference in subjects that are being caught and topics that aren't
are in the whitespace:
  rpms/bzrtools/devel bzrtools.spec,1.20,1.21
Not caught:
  rpms/bzr/EL-5 .cvsignore, 1.12, 1.13 bzr.spec, 1.16, 1.17 sources,
1.12, 1.13

This is with any of the following regular expressions:
^.*,[ ]*([0-9]+\.[0-9]+|NONE),[ ]*([0-9]+\.[0-9]+|NONE)$
^.*,[ ]?([0-9]+\.[0-9]+|NONE),[ ]?([0-9]+\.[0-9]+|NONE)$
^.*, ?([0-9]+\.[0-9]+|NONE), ?([0-9]+\.[0-9]+|NONE)$

I've modified the regular expression to this:

and it now seems to catch both subjects with spaces between the version
numbers and subjects without.

- -Toshio
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]