On Tue, Oct 13, 2015 at 06:31:04PM +0000, Guenter Milde wrote: > On 2015-10-12, Jean-Marc Lasgouttes wrote: > > Le 12/10/2015 18:02, Guenter Milde a écrit : > >> Either the "soft release lock" is lifted somehow or somone else needs to > >> apply it... > > > I do not think that any lock has been put on you (yet? :p). > > I was asked not to commit anything until the issue is solved. > > > We can live with a few missing messages on lyx-cvs, as long as this > > gets sorted out eventually. > > > I propose that you commit your patches yourself and tell us about it on > > lyx-devel and that, in parallel, we try to fix this subscription problem. > > 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.
Agreed. I think everyone agrees that this is how it should work. The more relevant question is what to do considering it does not work that way. Fixing it would be nice but I don't even know who to contact about that. > 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 > > I can live withn just supplying pathches or with your proposed procedure > (post announcdement to lyx-devel manually). If we are not able to fix things, then I see two solutions: 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. JMarc proposed (2), if I understood correctly. I prefer (2) over (1) also. Any other opinions? Scott
