> (I am allowed to see it). I mean: (if I am allowed to see it.)
----- Uwe Schindler H.-H.-Meier-Allee 63, D-28213 Bremen http://www.thetaphi.de eMail: [email protected] > -----Original Message----- > From: Uwe Schindler [mailto:[email protected]] > Sent: Tuesday, October 19, 2010 11:21 PM > To: [email protected] > Subject: RE: possible to filter the output to commits@ list???? > > Hi Upayavira, > > Thanks for the hint. Indeed with changing the config file (which allows special > configs for specific subtrees of the svn, so we can do it only for Lucene), we can > do it very easy: > > http://opensource.perlig.de/svnmailer/doc-1.0/#groups-generate-diffs > > "The generate_diffs option defines which actions diffs are generated for. It > takes a space or tab separated list of one or more of the following tokens: > add, modify, copy, delete, propchange and none. > > If the add token is given and a new file is added to the repository, the svnmailer > generates a diff between an empty file and the newly added one. If the modify > token is given and the content of an already existing file is changed, a diff > between the old revision and the new revision of that file is generated. The > copy token only worries about files, that are copied and modified during one > commit. The delete token generates a diff between the previous revision of the > file and an empty file, if a file was deleted. > > If the propchange token is given, the svnmailer also takes care of changes in > versioned properties. Whether it should actually generate diffs for the property > change action depends on the other tokens of the generate_diffs list. The same > rules as for files apply, except that the svnmailer never generates property diffs > for deleted files" > > > If we change that config option and remove propchange, then the diffs would > not contain propchanges anymore. It would it only list as modified files, but > with that we can live. > > Grant: Can you send me a copy of the current config file of that tool? I could > create a patch! (I am allowed to see it). > > Uwe > > ----- > Uwe Schindler > H.-H.-Meier-Allee 63, D-28213 Bremen > http://www.thetaphi.de > eMail: [email protected] > > > > -----Original Message----- > > From: Upayavira [mailto:[email protected]] > > Sent: Tuesday, October 19, 2010 1:07 PM > > To: [email protected] > > Subject: Re: possible to filter the output to commits@ list???? > > > > FWIW, the commit notices are just an SVN post-commit hook that uses > > the > svn- > > mailer tool [http://opensource.perlig.de/svnmailer/]. I believe Grant > > has commit rights to that file - it is in the infra SVN right next to > > the old > asf-auth > > file. > > > > Right now I have no idea whether svn-mailer can support the kind of > filtering > > you are talking about, but there's no harm looking! > > > > Upayavira > > > > On Tue, 19 Oct 2010 06:45 -0400, "Michael McCandless" > > <[email protected]> wrote: > > > On Mon, Oct 18, 2010 at 3:03 PM, Grant Ingersoll > > > <[email protected]> > > > wrote: > > > > > > > It was just a bit of a shocker for me the first time I did it and > > > > I > see like 30 > > files changed when I only changed one file. > > > > > > Me too. In fact I think it's ridiculous -- violates principle of > > > least surprise. I shouldn't have to see such details of the source > > > control system's impl.... > > > > > > Furthermore, I think it may eventually turn into a serious perf > > > issue, since it seems to be an O(N^2) growth. We are at 7 emails > > > today, which was only 3 emails not long ago. Where will be be a few > > > months from now? (Though I guess it is bounded by the total number > > > of source files we have in 3.x...). > > > > > > Maybe svn is trying to tell us to release 4.0, heh ;) > > > > > > Mike > > > > > > -------------------------------------------------------------------- > > > - To unsubscribe, e-mail: [email protected] For > > > additional commands, e-mail: [email protected] > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] For > > additional commands, e-mail: [email protected] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] For additional > commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
