autoconf-patches
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Ping


From: Akim Demaille
Subject: Re: Ping
Date: Fri, 16 May 2003 12:34:35 +0200
User-agent: Gnus/5.1001 (Gnus v5.10.1) Emacs/21.3 (gnu/linux)

 Bonzini> Could anybody review and/or apply my patches to CVS (except
 Bonzini> maybe the shell function one, of course), so that I can move
 Bonzini> to other tasks such as documenting M4sh or adding more shell
 Bonzini> function usage?

Hi Paulo,

I should take some time to explain my problems.

They all come down to a single factor: time.  I'm overflowed by all
the messages I should answer to, all the work real life requires etc.
And sometimes there happen a couple of excellent ideas, that lead to
huge threads that I don't have time to review completely.  So they
remain pending until I come to them.

This is extremely bad, and I do not want to become a problem for
Autoconf.  I would really love to find a peer for the Autoconf design
per se, as specific macros are less a problem.

I enjoy your ideas, but as I had some thoughts about them too, I want
to discuss with you, have them evolve, and finally implement them
together.  But I do not want to make this before 2.58.  So first of
all, I would like to make Autoconf and Bison releases, and then dive
into more experimental things for Autoconf.

An option would be a separate branch.  I am not opposed to this idea.
This would give more freedom for experimentation, and make it easier
to "discuss" about code.

Still, I need help to flush the bug reports.  Nothing serious will
happen before we flush a large part of them.


PS/  I never forgot autolib, I love it, but gnulib happened in the
meanwhile, and I never had the time to see whether that would be a
duplicate effort, whether we should merge things etc.


PS2/  Please, subscribe on Savannah.  I don't have time to apply
other significant contributors' patches.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]