Re: gnulib strftime imported into Emacs

[Lennart Borgman]

On Mon, Jan 31, 2011 at 11:19 PM, Paul Eggert <address@hidden> wrote:
> On 01/31/11 03:06, Eli Zaretskii wrote:
>
>> I'm talking only about changes that are known in advance to break
>> some platform, and for which you are not providing the corresponding
>> changes as part of the changeset.  I'm asking whether it would be
>> possible to talk a short while before committing such changes,
>
> Sure, I can send out some email when I'm coding up changes.  It should
> be easy to do that, as part of normal development.
>
>> when you already have your feature branch ready to merge onto the trunk.
>
> This part sounds too strict, though.  Normally it takes quite some
> time to prepare the change precisely for the trunk.  I develop on RHEL
> 5.5 x86-64, but for nontrivial changes before committing I test on
> several other platforms that I have easy access to, including at least
> one non-GNU platform.  I don't want to have to do that work multiple
> times, as it takes far more work to prepare and test the changes
> than it does to code them up.
>
>> If the change needs non-trivial corresponding changes in the Windows
>> build process, I might indeed ask to wait a few days.
>
> This part worries me.  Mainline Emacs development shouldn't be held
> back because of a lack of resources to port it to Windows.


I do not want to take part in the C coding, but I wonder if it would
help you if other people had a checkout of your branch on w32 and at
least could test it? Do you have tests for it that we could run on
w32? (If you have it would be a small problem for me to run some tests
on w32.)