On Mon, Sep 09, 2013 at 11:06:46AM -0600, Eric Blake wrote:
On 09/09/2013 10:01 AM, Daniel P. Berrange wrote:
From: "Daniel P. Berrange" <berrange@redhat.com>
We are no longer using automake, so Makefile.am is obsolete
Signed-off-by: Daniel P. Berrange <berrange@redhat.com> --- Makefile.am | 172 ------------------------------------------------------------ 1 file changed, 172 deletions(-) delete mode 100644 Makefile.am
Of course, until patch 17, that means the tree is unbuildable. Do you need to rearrange your series? Is it worth trying to make any of this bisectable? Or are we okay just declaring that prior to 1.1.3, the libvirt-python.git repository is unbuildable as-is and is more just a historical snapshot of history for how it reached the point of independent building?
I can live with the line in the sand approach - builds prior to the split require use of libvirt.git.
To be clear - once you run 'git filter-branch' on the repo, it is not buildable in any way at all. So nothing in this series is bisectable from a build POV. Daniel -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|