Or you could try to see if some of the existing mergeinfo can be removed, and try to have less subtree mergeinfo in the first place; these are common topics on us...@subversion.
Uwe Schindler wrote on Sun, Oct 17, 2010 at 17:06:44 +0200: > Hi all, > > There are configuration options in SVN to let the commit mails pipe through a > filter. Other svn hosting providers like Sourceforge provide some filters to > be applied. Ideally, you would use the "patchutils" package (it's called like > this in Debian/Ubuntu) and use "svn diff | filterdiff --clean" and pipe that > into an eMail. Maybe we should open an issue at infra? > > Uwe > > ----- > Uwe Schindler > uschind...@apache.org > Apache Lucene PMC Member / Committer > Bremen, Germany > http://lucene.apache.org/ > > > -----Original Message----- > > From: Robert Muir [mailto:rcm...@gmail.com] > > Sent: Sunday, October 17, 2010 4:58 PM > > To: dev@lucene.apache.org > > Subject: possible to filter the output to commits@ list???? > > > > Lets say i change a single line of code, and merge it back to the 3x_branch. > > > > Currently we get 6 or 7 emails of mergeproperty changes to the commits@ > > list... this is making it difficult or impossible for backports to be > > reviewed at > > all... I think this is terrible. > > > > How can we get this fixed so that these mergeprop-changes only are filtered > > in > > the emails? Someone could always click the link to viewvc or whatever if > > they > > are interested in this... > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional > > commands, e-mail: dev-h...@lucene.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
