Hi Frank, well, all this is scripting, so sure it's possible. What we would need is a set of mappings of top-level directories to "projects". Well, to be exact four set of mappings, for example for svx
.../trunk/*/svx -> framework .../tags/*/svx -> framework .../cws/*/svx -> framework .../branches/*/svx -> framework The initial setup is probably not a big problem but I hate the idea of maintaining such mappings forever. But if someone comes up with a good idea how to do this automated, I'll implement this. Heiner Frank Schönheit - Sun Microsystems Germany wrote: > Hi Heiner, > >> notifications to [EMAIL PROTECTED] should work now. > > any chance of breaking this down? > > In the past, I used the CVS mailing list to monitor commits to my > project (to a certain degree, at least), and AFAIK others were doing > this, too. > > allsvn, I suppose, will spam me with zillions of mails, and I'd like to > avoid retrieving all those mails, just to delete nearly all of them > immediately. > > I know that for SVN, the notion of project and module is meaningless, so > anything to set up here is certainly non-trivial. Nonetheless, it would > be useful to have some kind of subscription to a subset of allsvn. > > Any plans for this? > > Ciao > Frank > -- Jens-Heiner Rechtien [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
