On 2015-10-14, Georg Baum wrote: > Scott Kostyshak wrote: >> On Tue, Oct 13, 2015 at 06:31:04PM +0000, Guenter Milde wrote: >>> On 2015-10-12, Jean-Marc Lasgouttes wrote:
... >>> I believe that any commit message should go to lyx-cvs, just check for >>> some sign that this is an auto-generated message from the versioning >>> system. Authorisation is checked by the VS already. >>> Actgually, if there were unauthnorized activity on the repository, it >>> would be even more important to get this known on lyx-cvs. > lyx-cvs is not a security device. Of course not. However, there is no reason at all to have auto-generated commit messages from the repository returned from the lyx-cvs list. ... >>> Therefore, I don'tg want to waste time in trying to find out how I can >>> subscribe to a list and set up a spam filter to reliably kill the >>> incoming messages. >> OK > We are talking about a one time effort of at most half an hour for one > person only. Subscribing to lyx-cvs with lyx.org addresses works in general > (one could ask Guillaume how he did it if it is unclear how it works), and > setting up a filter in the google mail account is easy as well. > Please relate this effort to the time which is wasted by requiring other > developers to work around that personal preference. I tried to play nice. It actually took months (if not years) until the known preconditions for comitting to the LyX repo were up and working (of course I did also something else inbetween). I spend hours setting up, activating, reactivating this lyx.org mail account and setting up a forwarding, because I was told this is required to get commit rights. After my first commit, I was told: you must also subscribe to lyx-cvs (a list I don't want to get). Reluctantly, I tried also to hop through this next loop but failed. Also, my fixes were incomplete, because some tests did not run any more. There was no documentation about tests, no documentation about the need to subscribe to lyx-cvs. Pausing and reconsidering, I come to the conclusion: >>> I can live with just supplying patches. ... >> 1. You post your patches and then other LyX developers commit your >> patches. >> 2. You commit your patches and you send an email with the exact same >> patch you just committed. This notifies everyone of your commit and also >> allows us to easily comment on the code if we choose to. ... > 1) is a waste of time IMHO and effectively revoking commit privileges (which > is not a good idea either). > 2) is a good temporary workaround, but not a long term solution IMHO. I don't know the complete picture of the LyX code, so someone has to go through and audit my patches anyway, so 1) is the "safe bet". The patches are on the LyX bug-tracker ready for examination and application. Günter
