Update the README.

README

@@ -45,10 +45,20 @@ http://hg.et.redhat.com/virt/applications/virtinst--devel
 Contact
 -------
 
-All comments / suggestions / patches should be directed to the fedora-xen
+All comments / suggestions / patches should be directed to the et-mgmt-tools
 mailing list:
 
-  http://www.redhat.com/mailman/listinfo/fedora-xen
+  http://www.redhat.com/mailman/listinfo/et-mgmt-tools
+
+Bugs should be reported at bugzilla.redhat.com, against the 'virt-manager'
+component.
+
+If you built from source, use Product: 'Virtualization Tools'.
+
+If you are using a package provided by Fedora, use Product: 'Fedora'.
+
+If you are using another distros package, either file a bug with them,
+or use the 'Virtualization Tools' product as above.
 
 There are further project details on the website:
 
@@ -73,11 +83,10 @@ the main source repository:
    hg clone  http://hg.et.redhat.com/virt/applications/virt-manager--devel
    cd virt-manager--devel
    ... make some changes & commit them locally...
-   hg bundle myfeature.hg http://hg.et.redhat.com/virt/applications/virt-manager--devel
+   hg export -r my_feature_revision > my_feature.patch
 
-Then mail the 'myfeature.hg' file to fedora-xen list. This approach is
+Then mail the 'myfeature.patch' file to et-mgmt-tools list, with [PATCH]
-preferred to plain patches, because the Mercurial bundle preserves all
+and a brief description in the subject.
-your local commit messages & history.
 
 Related software
 ----------------
@@ -85,6 +94,7 @@ Related software
 Links which are relevant:
 
   http://libvirt.org
+  http://www.linux-kvm.org
   http://xensource.com/xen/
   http://pygtk.org/
   http://gtk.org/