Re: [vdsm] VDSM Repository Reorganization

: * No-one read it * No-one understood it * No-one cared * No-one is paying attention to you any more * It's so ridiculous it's unworthy of comment * Everyone who read it agrees I suggest you assume the last one, and proceed until someone starts shouting at you ;-) Thanks, Dave. -- Dave Neary

Re: [vdsm] VDSM - top 10 with patches with no activity for more than 30 days

. Is there a way we can promote adopt a patch where you take someone else's patch and push it through review? Cheers, Dave. -- Dave Neary - Community Action and Impact Open Source and Standards, Red Hat - http://community.redhat.com Ph: +33 9 50 71 55 62 / Cell: +33 6 77 01 92 13

Re: [vdsm] vdsm - closer to open source versioning and release cycle

. The development should happen on feature branches, merged into master. Branches should only be created for a release when it is in pre-release stabilisation (so, after feature API freeze). Cheers, Dave. -- Dave Neary - Community Action and Impact Open Source and Standards, Red Hat - http

[vdsm] oVirt developer meeting @ KVM Forum

interest, and for your support of oVirt! Regards, Dave Neary. -- Dave Neary - Community Action and Impact Open Source and Standards, Red Hat - http://community.redhat.com Ph: +33 9 50 71 55 62 / Cell: +33 6 77 01 92 13 ___ vdsm-devel mailing list vdsm-devel

Re: [vdsm] stale gerrit patches

is the place for in-progress patches (use private branches for that). Cheers, Dave. -- Dave Neary - Community Action and Impact Open Source and Standards, Red Hat - http://community.redhat.com Ph: +33 9 50 71 55 62 / Cell: +33 6 77 01 92 13 ___ vdsm-devel