[Ovirt-devel] Re: [PATCH ovirt-node] Adds automatic non-interactive configuration for the standalone node.

Alan Pevec apevec at redhat.com
Tue Nov 18 00:15:52 UTC 2008

Jim Meyering wrote:
> With iteration upon iteration like this, you can see
> how using a shared development/unstable/pu branch (with very
> permissive "push" policy) might help.

let's try this, I've created ovirt-node fork at:


master branch there is next + outstanding patches for ovirt-node which I think are ready for ack
NB: this branch can be rebased at anytime!

Please register at repo.or.cz and tell me your login to give you rw right.
Then you can, in your ovirt-node git checkout:
(initial push)
git remote add TEMP ssh://repo.or.cz/srv/git/ovirt-node/TEMP.git
git push TEMP YourLocalBranchYouWantToShareWithEverybody:refs/heads/yourreporczlogin

More information about the ovirt-devel mailing list