lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Grant Ingersoll <>
Subject Re: mergeinfo commit mails, possible solution
Date Wed, 17 Nov 2010 13:53:07 GMT

On Nov 17, 2010, at 1:01 AM, Steven A Rowe wrote:

> After looking more closely at the vanilla Subversion version of the script,
I'm 99% sure that removing propchange from the generate_diffs list will have zero effect,
but I'd love to be proven wrong.
> Turns out Subversion's once had a much larger set of property filtering options,
but C. Mike (Pilato) thought the option set was too baroque, so he reverted the entire set
- see <>.
> I've asked on #svn about re-instating the "ignore_props" and "ignore_propdiffs" regex-valued
options - these would allow us to only ignore svn:mergeinfo diffs while still noting that
files' properties have changed, without affecting other properties or their diffs.  No responses
yet, hopefully tomorrow.

We might also be able to supply a patch to ASF infra to turn it on.

However, I still feel like we are doing something wrong here relative to other projects. 
Surely other projects are doing merges and have successfully avoided all this noise.  (I know,
I know, we've discussed this before.)  Perhaps an email to community@a.o might help or if
we look around at other projects that merge and see what they do.  In looking in the mailer
conf, some projects turn off generating diffs altogether, but I don't think that is what we

FWIW, it was announced at ApacheCon that the ASF will be supporting Read/Write Git, so maybe
we just live with it until we can migrate to Git.


> Steve
>> -----Original Message-----
>> From: Grant Ingersoll []
>> Sent: Tuesday, November 16, 2010 9:55 AM
>> To:
>> Subject: mergeinfo commit mails, possible solution
>> From #lucene IRC:
>> gsingers:sarowe and I were talking about the mergeinfo commit overload
>> [09:43]gsingers:and the asf_mailer.conf file
>> [09:43]gsingers:In looking at the file
>> [09:44]gsingers:it appears the one thing we have the ability to do is to
>> turn off the generation of diffs for
>> [09:44]gsingers:events
>> [09:44]gsingers:The default setting is:
>> [09:44]gsingers:generate_diffs = add copy modify propchange
>> [09:44]gsingers:sarowe and I are proposing to change our settings to just
>> be add/copy/modify
>> [09:44]gsingers:and try dropping propchange
>> [09:45]gsingers:I honestly don't know whether it will work or not
>> [09:45]gsingers:and it will also likely mean we will miss notifications of
>> other propchanges
>> [09:45]gsingers:We've asked on #asfinfra if there are other options
>> [09:45]gsingers:and sarowe is looking into the script to see if
>> there are other things available
>> [09:46]gsingers:I guess the question here is, do people want to try
>> turning off propchange?
>> -Grant
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail:
>> For additional commands, e-mail:

Grant Ingersoll

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message