On Mon, Jan 14, 2008 at 01:56:15PM +0000, Daniel P. Berrange wrote: > On Mon, Jan 14, 2008 at 12:35:45PM +0000, Richard W.M. Jones wrote: > > Jim Meyering wrote: > > >I ran ./bootstrap against a just-updated gnulib directory, so these > > >changes now sync into libvirt all of the changes from gnulib since > > >the last time: > > > > > > Update from gnulib. > > > > > >FYI, nearly all of these changes are also in the latest coreutils > > >beta/test release, so if there are problems, I should hear about > > >it soon. > > > > > >If you'd like to see justification for a particular change, > > >you'll probably find it in a combination of these: > > > > > > gnulib's ChangeLog file > > > a unit test change or addition, > > > a message on the bug-gnulib mailing list. > > > > +1. Should integrate early as possible into libvirt so that we get most > > testing. > > ACK. > > Should we have a general rule that we always do a gnulib update immediately > after we put out a libvirt release ? That gives us reasonably frequent > updates while allowing a good amount of in-tree time for testing... Yup, sounds a good idea to proceed that way Daniel -- Red Hat Virtualization group http://redhat.com/virtualization/ Daniel Veillard | virtualization library http://libvirt.org/ veillard@xxxxxxxxxx | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/ -- Libvir-list mailing list Libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list