RE: [JBoss-dev] CVS updates vs dev talk
Hello, This has already been discussed a few times. The best solution would be to split the ML: one for dev-posts and one for dev-cvs. But I would keep the format of CVS messages: it is useful to see the content of what has been modified. In the meantime, do like everybody: create a rule in your e-mail software that will automatically move the CVS log messages in another folder. If your concern is not about Internet bandwidth, then I am sure the result will be the same in your e-mail client software as if we had two distincts ML: one folder for each ML. Cheers, Sacha > -Message d'origine- > De : [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]De la part de > Tilly, Jesse > Envoyé : lundi, 26 novembre 2001 18:20 > À : '[EMAIL PROTECTED]' > Objet : [JBoss-dev] CVS updates vs dev talk > > > Is there a way for us to separate the messages that go into the current > digest to go into two digests? One for CVS updates and one for normal > development discussions? I've been monitoring the digest for over two > weeks. 80% of the messages are CVS commit updates, which, while > informative > for those looking for changes, are very bad on the eyes since they're in a > raw format. If anything, can we turn the CVS update message into > something > that just contains the committer's comments? Seems to be a very > high noise > ratio here. ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] CVS updates vs dev talk
The problem isn't the filtering of the messages. I get the digest which contains everything. I would have to parse each message and remove everything from line x to line y when subject was "CVS*". The concern is that the digest is getting filled up and isn't really much of a digest. I guess the only solution is to subscribe to the full thing and do the subject filter. Jesse > -Original Message- > From: Sacha Labourey [mailto:[EMAIL PROTECTED]] > Sent: Monday, November 26, 2001 12:27 PM > To: Tilly, Jesse; [EMAIL PROTECTED] > Subject: RE: [JBoss-dev] CVS updates vs dev talk > > > Hello, > > This has already been discussed a few times. The best > solution would be to > split the ML: one for dev-posts and one for dev-cvs. > > But I would keep the format of CVS messages: it is useful to > see the content > of what has been modified. > > In the meantime, do like everybody: create a rule in your > e-mail software > that will automatically move the CVS log messages in another > folder. If your > concern is not about Internet bandwidth, then I am sure the > result will be > the same in your e-mail client software as if we had two > distincts ML: one > folder for each ML. > > Cheers, > > > Sacha > > > > > -Message d'origine- > > De : [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED]]De la part de > > Tilly, Jesse > > Envoyé : lundi, 26 novembre 2001 18:20 > > À : '[EMAIL PROTECTED]' > > Objet : [JBoss-dev] CVS updates vs dev talk > > > > > > Is there a way for us to separate the messages that go into > the current > > digest to go into two digests? One for CVS updates and one > for normal > > development discussions? I've been monitoring the digest > for over two > > weeks. 80% of the messages are CVS commit updates, which, while > > informative > > for those looking for changes, are very bad on the eyes > since they're in a > > raw format. If anything, can we turn the CVS update message into > > something > > that just contains the committer's comments? Seems to be a very > > high noise > > ratio here. > ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] CVS updates vs dev talk
Jesse, Sorry for not having fully understood/read what you problem was: I thought you were receiving the messages, not the digest. I now understand your problem, and it is a real one! ;) Good luck. Cheers, Sacha > -Message d'origine- > De : Tilly, Jesse [mailto:[EMAIL PROTECTED]] > Envoyé : lundi, 26 novembre 2001 19:10 > À : 'Sacha Labourey'; Tilly, Jesse; > [EMAIL PROTECTED] > Objet : RE: [JBoss-dev] CVS updates vs dev talk > > > The problem isn't the filtering of the messages. I get the digest which > contains everything. I would have to parse each message and remove > everything from line x to line y when subject was "CVS*". The concern is > that the digest is getting filled up and isn't really much of a digest. > > I guess the only solution is to subscribe to the full thing and do the > subject filter. ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] CVS updates vs dev talk
yOn Mon, 26 Nov 2001, Tilly, Jesse wrote: > The problem isn't the filtering of the messages. I get the digest which > contains everything. I would have to parse each message and remove > everything from line x to line y when subject was "CVS*". The concern is > that the digest is getting filled up and isn't really much of a digest. formail(from procmail) can do this for you. :0 HE * ^X-Mailing-List: .*[<].*-digest@lists\.debian\.org[>] * ^X-Mailing-List: .*[<] *\/[^ ][^@]* |formail +1 -a "X-Mailing-List: <`echo $MATCH|sed 's/-digest$//'@lists.debian.org>" |-ds procmail This rule matches anything sent from [EMAIL PROTECTED] It then changes the ender of each internal mail(in the digest) to [EMAIL PROTECTED], so that other rules can than filter it to the correct location. ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
