[MPlayer-cvslog] r19839 - in trunk: DOCS/man/en/mplayer.1 DOCS/tech/slave.txt input/input.c libmpcodecs/vf_screenshot.c mplayer.c

Diego Biurrun diego at biurrun.de
Sat Sep 16 23:32:30 CEST 2006

On Fri, Sep 15, 2006 at 07:52:07PM -0400, The Wanderer wrote:
> Corey Hickey wrote:
> >The Wanderer wrote:
> >>Okay, I've been wondering for a while now - how does this happen? I
> >>have two - or actually three, if you count the one on -DOCS -
> >>different commit E-mails with the same revision number and commit
> >>messages, but different listed changes (to different sets of files,
> >>to boot). I've noticed this or variations thereof (I don't remember
> >>which) on several occasions, and still have the relevant mails in
> >>my archive if I have any reason to dig them up.
> >
> >I would guess this is a result of rules on the server specifying that
> >modifications to different parts of the repository go to different
> >mailing lists. The rules which affected this commit are:
> >
> >trunk/DOCS/tech    ---   mplayer-cvslog
> >trunk/DOCS         ---   mplayer-DOCS
> >trunk/             ---   mplayer-cvslog
> >
> >Apparently even though trunk/ and trunk/DOCS/tech both go to -cvslog,
> >there were two different mails sent here because the commit matched
> >both the first and the third rule I listed above.
> Ah. That would explain it. It still seems strange, but at least it's not
> a misbehaviour as such.
> It would be nice if it were possible to tell, just from looking at a
> particular commit notification, which chunk it was supposed to be
> associated with...
> Where exactly are these rules stored? If possible, I'd like to have a
> look at the full list for myself.

conf/mailer.conf in the MPlayer repository, here's the relevant part:

# some advanced Python RE stuff in here ...
# http://www.amk.ca/python/howto/regex/
# http://docs.python.org/lib/re-syntax.html

for_paths =
to_addr = mplayer-docs at mplayerhq.hu

for_paths = trunk/DOCS/tech/(?!nut.txt$)
to_addr = mplayer-cvslog at mplayerhq.hu

for_paths = trunk/DOCS/tech/nut.txt
to_addr = nut-devel at mplayerhq.hu

#for_paths =
for_paths =
to_addr = mplayer-translations at mplayerhq.hu

The [tech] section is bogus on second thought.


More information about the MPlayer-cvslog mailing list