Dear LyX developers,
On 2015-10-16, Guillaume Munch wrote:
> Le 16/10/2015 18:10, Guenter Milde a écrit :
>> Georg wrote:
>>> We are talking about a one time effort of at most half an hour for
>>> one person only.
...
>>> Please relate this effort to the time which is wasted by requiring
>>> other developers to work around that personal preference.
I see it rather as a one-time effort to get the lyx-cvs permissions right.
The additional loop ("... and, btw., you need to subscribe to this list if
you really want to commit") after finally getting commit rights set up and
working will hit other future contributors, too.
With Git, the commit history is on my machine without the need for an
additional list-subscription and there are plenty of tools to comfortably
browse it. (A release manager might profit from alerts for all commit
activity, but not a casual supporter like me.)
...
> I cannot see what can go wrong with subscribing to lyx-cvs. Tell us more
> if something went wrong.
I don't want to use the gmail interface. When I was told that I need this
mail at google, I planned to set the forwarding and don't touch this any
more. Consequently I don' remember the password. Considering the whole
procedure of subscribing to a list only to throw away the resulting
messages as fundamentally wrong, I don't want to retrieve a password only
to actually do this fundamentally wrong action.
The lyx-lists page lists some commands one can sed to the list manager to
get help or perform actions, also a syntax for doing this from/for
another mail address. I tried to get the help message from lyx-cvs
several times but without response. After thnis failure, I did not follow
up with a subscription request.
>> Pausing and reconsidering, I come to the conclusion:
>>>>> I can live with just supplying patches.
>> 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".
> I don't see the link with people anyway reading your code. Ultimately
> the other devels rely on you for code quality. “Audit” is a bit of an
> overstatement. For instance, the devel FAQ promised me “a lot of
> comments” about my code, but I have not seen that happen.
Well, I got them. My first, very simple and "innocent" commit broke a
test. It is the reason for this thread: people relied on lyx-cvs instead
of the git log and so this little change (one additional definition
in lib/unicodesymbols) went unnoticed.
Unfortunately, there is also no agreement on the way out, as the proper
fix requires changing unicodesymbols, tex2lyx, and test-files (bugs in
the expected test outcome).
>> The patches are on the LyX bug-tracker ready for examination and
>> application.
...
> I understand that this bureaucratic stuff evokes bad memories for you,
> but you could give it one more try.
I'll try workaround 2) sometimes in the next days...
Thanks for the patience and encourfagement,
Günter
