On Wed, Mar 23, 2016 at 06:46:53PM +0000, Daniel P. Berrange wrote:
> On Wed, Mar 23, 2016 at 04:34:26PM +0100, Kashyap Chamarthy wrote:
> [snip]
>
> So things turn out to be a bit more complicated for libvirt than for
> QEMU, because we have one mailing list accepting patches for 10+
> different git repositories.
Ah-ha, good point.
> Patches has no built-in support for this
> model, so you have to create a separate configuration file for each
> repo, so that it stores the patches json file separately for each
> and then pass that config file when fetching
>
> git clone
git://github.com/stefanha/patches.git
>
> REPOS="libvirt libvirt-designer libvirt-glib libvirt-java
> libvirt-perl libvirt-php libvirt-python libvirt-sandbox
> libvirt-snmp libvirt-tck"
> for repo in $REPOS
> do
> cat > $HOME/.patchesrc-$repo <<EOF
> [options]
> patches_dir=$HOME/.patches/$repo
>
> [fetch]
>
url=http://libvirt.org/patches/$repo/patches.json
> EOF
Yeah, this nicely solves it currently, thanks for clearly spelling it
out.
How often are the JSON databases updated? Once daily at least, I
presume.