Re: Noisy byte compilation on master

[Stefan Monnier]

>> Or you could use a macro which either drops the name argument or passes
>> it depending on the version of EIEIO with which it's compiled.
> I would still have to rewrite the constructor calls, right?

Yes, but it should be a slightly simpler rewrite (no need to find&remove
the name string).

> Remember that I did merges maybe every few months. I had a ton of
> entries for the same day as result, containing things like
>  (foo): Change 'a' to 'c'.
>  (foo): Revert previous change.
>  (foo): Change 'a' to 'b'.
> I was under the impression that stuff like this had to be cleared up.

It's better good if you do, but it's not indispensable.

> Sorry, I didn't know that all this could be handled automatically.  I was
> under the impression that I'd still have to edit the generated logs.

The generation would happen as part of creating the tarball of
a release, so you wouldn't have the opportunity to edit it.


        Stefan