On Sun, Jun 19, 2011 at 05:15:55AM -0400, Itamar Heim wrote: > > > > -----Original Message----- > > From: libvir-list-bounces@xxxxxxxxxx > [mailto:libvir-list-bounces@xxxxxxxxxx] On Behalf Of Daniel Veillard > > Sent: Thursday, June 09, 2011 16:20 PM > > To: libvir-list@xxxxxxxxxx > > Subject: Availability of patchchecker > > Hopefully it may prove useful to a few of us, and possibly be > > adapted to other projects (as usual I take patches :-) > > Just wondering - why not go with a tool more oriented at this like gerrit? Oh, very simple, I want patch handling to not change at all, we are way more comfortable with mail based processing than having to go on the web to click on things, as stated I want something which helps, not get on the way :-) This is a status report only tool, but automatic, i.e. it finds the patches itself, it finds the commits itself, something like http://source.android.com/source/life-of-a-patch.html means the tool becomes central to managing patches and that's not what we want. So yes it is a different use, actually patchchecker never touches or look at the content of patches, it just reconstruct the flow based on completely public informations. Daniel -- Daniel Veillard | libxml Gnome XML XSLT toolkit http://xmlsoft.org/ daniel@xxxxxxxxxxxx | Rpmfind RPM search engine http://rpmfind.net/ http://veillard.com/ | virtualization library http://libvirt.org/ -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list