* Eric Blake wrote on Sun, Apr 19, 2009 at 01:03:20AM CEST: > According to Ralf Wildenhues on 4/18/2009 4:45 PM: > > Running 'make autom4te-update' in git Autoconf currently exposes two > > issues: move-if-change may not be found but needed (oh well), and > > gnulib has the current version of move-if-change. Do we need to import it > back into autoconf to keep the 'autom4te-update' target happy?
Well, my git Autoconf tree doesn't have the file at all. Do I need some magic gnulib-tool incantation to import it, and if yes, maybe Autoconf should have a bootstrap script to abstract this away? > > OK to push, and afterwards commit the result of "make autom4te-update" > > to Autoconf? Note that there is no relevant difference between the > > Automake git branches "master" and "next" in this area. > > Yes, and thanks for resynchronizing this bit. Thanks, done. I've taken liberty to _not_ synchronize the GPLv3+ headers which are present in git Automake, so updating in Autoconf can be done at once. Cheers, Ralf
