Hi Uwe, >>>>> Uwe Brauer <o...@mat.ucm.es> writes: >> You can send patches without a working repository; would produce a >> little more work at the maintainer side, but it is doable.
> Well, I really feel uncomfortable using code which could not be tested > against the latest repository commit, by running make, Well, I don't understand what you are afraid of because ELPA-devel is the same as the latest git repository. You don't have to run make on it. > yet providing such code seems more problematic It is true that you have to byte-compile the new code manually in order to test it and you cannot use "make" for byte compile after you switch to using ELPA-devel. But is isn't "problematic" in my view. >> Sorry, no idea. But I'd say the change wasn't so drastic as you think, >> so I really can't tell why you can't build from a fresh clone. > Because it builds some variable from some git meta data which do not > exist in a mercurial clone. I don't understand this, either. The commit by Stefan did not change anything with respect to the data extraction from .git directory. Regards, Ikumi Keita #StandWithUkraine #StopWarInUkraine #Gaza #StopMassiveKilling #CeasefireNOW
