[Xen-API] A few direct pushes to xen-api

[Jon Ludlam <jonathan.ludlam@xxxxxxxxxxxxx>]

Hi guys,

If anyone is following xen-api closely on github, you'll notice a few 
changes that have gone in this morning without the usual pull request. 
Apologies for this, but there's been a very small amount of divergence 
and an internal process wrinkle that have necessitated these:
1. 4 new commits that came in 'by the back door', and haven't gone 
through the usual pull request procedure. This was simply human error. 
For reference, those commits are:
 584584570357127c663d1561791a9f13d2616d72
 ebf46c4c045b6bc58fd2d1c99ce971479109080e
 ad8afdee490dc0dbbf62f7570e828175b3aaff3d
 91704a674933273c7ae1d31f47cbdcb77c79f0b9

2. There are several merge commits - these are as a result of the above 
commits.
3. There are two changesets that revert and then re-apply a bunch of 
commits. Taken together, they are a no-op. This was applied simply as a 
convenience to work around some internal tools that can't cope with 
repositories losing commits. Changesets are:
f966c0e16487c7f588cbe3875236117c803b3df4
4db8dd86d2ef788d35065d91bef84d1213e78ed4

We'll try hard in future to make sure this sort of thing doesn't happen 
again.
Cheers,

Jon


_______________________________________________
Xen-api mailing list
Xen-api@xxxxxxxxxxxxx
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api