Hi Erik, all, I would like to revive the thread below. So you know we are already using this modified version across 3/4 different projects in 2 public organizations. I am wary of maintaining and distributing the fork myself.
Would you want to guide me through the process of updating this patch to whichever branch will released next? I would need to know: 1) which branch: 1.4, 1.6, other? 2) which repo? (I have git://git.sv.gnu.org/m4; is this still the right place?) 3) anything else besides the code and m4.info diffs I should care about? ChangeLog maybe? 4) once updated, in which form do you want to receive the patch? On Mon, Nov 1, 2010, at 17:28, Eric Blake wrote: > On 10/30/2010 06:54 AM, Raphael 'kena' Poss wrote: > > Dear all, > > > > I posted the mail below to m4-patches a while ago, but I haven't seen any > > reaction; did my mail server do anything wrong? > > No, the mail came through just fine; as did your copyright assignment > paperwork. It's just that my current m4 development time has been very > limited :( > > It's definitely on my radar, and certainly less controversial than the > proposed patches for adding makefile dependency tracking support. > > -- > Eric Blake ebl...@redhat.com +1-801-349-2682 > Libvirt virtualization library http://libvirt.org > > Email had 1 attachment: > + signature.asc > 1k (application/pgp-signature) _______________________________________________ M4-patches mailing list M4-patches@gnu.org https://lists.gnu.org/mailman/listinfo/m4-patches
