Maintainer rights on vdsm - ovirt-3.5-gluster

Hi! On the vdsm branch "ovirt-3.5-gluster", could you provide merge rights to Bala (barumuga@redhat.com) ? thanks sahina

On 04/20/2015 04:36 PM, Dan Kenigsberg wrote:
On Mon, Apr 20, 2015 at 03:20:18PM +0530, Sahina Bose wrote:
Hi!
On the vdsm branch "ovirt-3.5-gluster", could you provide merge rights to Bala (barumuga@redhat.com) ? +1 from me.
ovirt-3.5-gluster needs a rebase on top of the current ovirt-3.5
Hi! Is there a push right to be enabled on this branch as well? Currently, rebasing and pushing is failing with following: remote: Branch refs/heads/ovirt-3.5-gluster: remote: You are not allowed to perform this operation. remote: To push into this reference you need 'Push' rights. remote: User: bala remote: Please read the documentation and contact an administrator remote: if you feel the configuration is incorrect remote: Processing changes: refs: 1, done To ssh://bala@gerrit.ovirt.org:29418/vdsm.git ! [remote rejected] ovirt-3.5-gluster -> ovirt-3.5-gluster (prohibited by Gerrit) error: failed to push some refs to 'ssh://bala@gerrit.ovirt.org:29418/vdsm.git'

--xXmbgvnjoT4axfJE Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable You want also push rights? It's not the same submit, push, create reference, verify, code review. All those are different rights. I've added the submit, code-review and veri= fy rights. Let me know if you want also the rest. Also note that pushing and submitting is not the same, pushing will skip ge= rrit and any gerrit checks, so it's usually something to avoid. While submitting= is done through gerrit, what allows gerrit to check validity of the code to be merged (gerrit hooks, updating bugzillas, jenkins jobs, signed-by flabs). On 04/29, Sahina Bose wrote:
=20 On 04/20/2015 04:36 PM, Dan Kenigsberg wrote:
On Mon, Apr 20, 2015 at 03:20:18PM +0530, Sahina Bose wrote:
Hi!
On the vdsm branch "ovirt-3.5-gluster", could you provide merge rights = to Bala (barumuga@redhat.com) ? +1 from me.
ovirt-3.5-gluster needs a rebase on top of the current ovirt-3.5 =20 Hi! =20 Is there a push right to be enabled on this branch as well? =20 Currently, rebasing and pushing is failing with following: =20 remote: Branch refs/heads/ovirt-3.5-gluster: remote: You are not allowed to perform this operation. remote: To push into this reference you need 'Push' rights. remote: User: bala remote: Please read the documentation and contact an administrator remote: if you feel the configuration is incorrect remote: Processing changes: refs: 1, done To ssh://bala@gerrit.ovirt.org:29418/vdsm.git ! [remote rejected] ovirt-3.5-gluster -> ovirt-3.5-gluster (prohibited by Gerrit) error: failed to push some refs to 'ssh://bala@gerrit.ovirt.org:29418/vdsm.git' =20
Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
--=20 David Caro Red Hat S.L. Continuous Integration Engineer - EMEA ENG Virtualization R&D Tel.: +420 532 294 605 Email: dcaro@redhat.com Web: www.redhat.com RHT Global #: 82-62605 --xXmbgvnjoT4axfJE Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJVQJFjAAoJEEBxx+HSYmnDTnAIAKBUj2LRrJLp89JbZq8BU2SK n/6rxnppKNvwO9aaZIjDCoXl7dq9Zo6UoZg290O0YM+fQUl5ZfpbW4MOGVVIoUkx wkh1FaZ4N5TofcjsXUtdc+akWfQ02AEUfyQVbOH1nkBgFjguQFNFgYnCl1/sfYqa +DxV3S1aonXxDEgSDbkMd2vqpZ7l0chx9Is+jOaFkVyVOJLcZ9N//HjPLAXMpKVK qAFHMm2vfQAhxk1NA5wcyQVOhHLdLJeMFKQ5R40Eft1f1wHwNRw+fKi7Z3+8zzsM kBYuXaIDjhxOHzu5aixmDeDc8X4yEk2rf9TXVYTtaQUvUlFq+EJAODnZltYxHbw= =csmz -----END PGP SIGNATURE----- --xXmbgvnjoT4axfJE--

----- Original Message -----
From: "David Caro" <dcaro@redhat.com> To: "Sahina Bose" <sabose@redhat.com> Cc: "Dan Kenigsberg" <danken@redhat.com>, infra@ovirt.org, "Balamurugan Arumugam" <barumuga@redhat.com>, devel@ovirt.org Sent: Wednesday, April 29, 2015 1:38:03 PM Subject: Re: Maintainer rights on vdsm - ovirt-3.5-gluster
You want also push rights? It's not the same submit, push, create reference, verify, code review.
All those are different rights. I've added the submit, code-review and verify rights. Let me know if you want also the rest.
Also note that pushing and submitting is not the same, pushing will skip gerrit and any gerrit checks, so it's usually something to avoid. While submitting is done through gerrit, what allows gerrit to check validity of the code to be merged (gerrit hooks, updating bugzillas, jenkins jobs, signed-by flabs).
The idea behind push right is that we would do periodical rebase of ovirt-3.5-gluster branch with ovirt-3.5 branch. Is this recommended way to do that? Regards, Bala
On 04/29, Sahina Bose wrote:
On 04/20/2015 04:36 PM, Dan Kenigsberg wrote:
On Mon, Apr 20, 2015 at 03:20:18PM +0530, Sahina Bose wrote:
Hi!
On the vdsm branch "ovirt-3.5-gluster", could you provide merge rights to Bala (barumuga@redhat.com) ? +1 from me.
ovirt-3.5-gluster needs a rebase on top of the current ovirt-3.5
Hi!
Is there a push right to be enabled on this branch as well?
Currently, rebasing and pushing is failing with following:
remote: Branch refs/heads/ovirt-3.5-gluster: remote: You are not allowed to perform this operation. remote: To push into this reference you need 'Push' rights. remote: User: bala remote: Please read the documentation and contact an administrator remote: if you feel the configuration is incorrect remote: Processing changes: refs: 1, done To ssh://bala@gerrit.ovirt.org:29418/vdsm.git ! [remote rejected] ovirt-3.5-gluster -> ovirt-3.5-gluster (prohibited by Gerrit) error: failed to push some refs to 'ssh://bala@gerrit.ovirt.org:29418/vdsm.git'
_______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
-- David Caro
Red Hat S.L. Continuous Integration Engineer - EMEA ENG Virtualization R&D
Tel.: +420 532 294 605 Email: dcaro@redhat.com Web: www.redhat.com RHT Global #: 82-62605

--4Epv4kl9IRBfg3rk Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 04/29, Balamurugan Arumugam wrote:
=20 =20 ----- Original Message -----
From: "David Caro" <dcaro@redhat.com> To: "Sahina Bose" <sabose@redhat.com> Cc: "Dan Kenigsberg" <danken@redhat.com>, infra@ovirt.org, "Balamurugan= Arumugam" <barumuga@redhat.com>, devel@ovirt.org Sent: Wednesday, April 29, 2015 1:38:03 PM Subject: Re: Maintainer rights on vdsm - ovirt-3.5-gluster =20 You want also push rights? It's not the same submit, push, create refer= ence, verify, code review. =20 All those are different rights. I've added the submit, code-review and = verify rights. Let me know if you want also the rest. =20 =20 Also note that pushing and submitting is not the same, pushing will skip gerrit and any gerrit checks, so it's usually something to avoid. While submit= ting is done through gerrit, what allows gerrit to check validity of the code t= o be merged (gerrit hooks, updating bugzillas, jenkins jobs, signed-by flabs= ). =20 =20 The idea behind push right is that we would do periodical rebase of ovirt= -3.5-gluster branch with ovirt-3.5 branch. Is this recommended way to do t= hat? =20
Which kind of rebase? Does it require using --force?
Regards, Bala =20 =20 =20 =20
On 04/29, Sahina Bose wrote:
=20 On 04/20/2015 04:36 PM, Dan Kenigsberg wrote:
On Mon, Apr 20, 2015 at 03:20:18PM +0530, Sahina Bose wrote:
Hi!
On the vdsm branch "ovirt-3.5-gluster", could you provide merge rig= hts to Bala (barumuga@redhat.com) ? +1 from me.
ovirt-3.5-gluster needs a rebase on top of the current ovirt-3.5 =20 Hi! =20 Is there a push right to be enabled on this branch as well? =20 Currently, rebasing and pushing is failing with following: =20 remote: Branch refs/heads/ovirt-3.5-gluster: remote: You are not allowed to perform this operation. remote: To push into this reference you need 'Push' rights. remote: User: bala remote: Please read the documentation and contact an administrator remote: if you feel the configuration is incorrect remote: Processing changes: refs: 1, done To ssh://bala@gerrit.ovirt.org:29418/vdsm.git ! [remote rejected] ovirt-3.5-gluster -> ovirt-3.5-gluster (prohibit= ed by Gerrit) error: failed to push some refs to 'ssh://bala@gerrit.ovirt.org:29418/vdsm.git' =20
Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra =20 -- David Caro =20 Red Hat S.L. Continuous Integration Engineer - EMEA ENG Virtualization R&D =20 Tel.: +420 532 294 605 Email: dcaro@redhat.com Web: www.redhat.com RHT Global #: 82-62605 =20
--=20 David Caro Red Hat S.L. Continuous Integration Engineer - EMEA ENG Virtualization R&D Tel.: +420 532 294 605 Email: dcaro@redhat.com Web: www.redhat.com RHT Global #: 82-62605 --4Epv4kl9IRBfg3rk Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJVQKzEAAoJEEBxx+HSYmnDf5QIAIDVoqw5gQssEtb4QUriaquJ ZY/H480WC6a2g77GCw5I6cUakrlEd8gHbl6egVDzh7Hrevt4WZudwWcWyjoyzF0f 24enI/8fSBEQRCEpCt9dJEifIcGUOh8ycRJSUoMiAUZdx+ch1TBQuNQn9WurXmcH z2iwvmppT29R8EprabYARnke/4ihxxcTkfM9svD9QEOa6Wk4K8tBqpepAZkFthWK TaPTa0AmZ00io9wZDXksqgLwRtU0tL24lhK2K3Ea91UAI8GMrMq9zfCfEO3yt6d1 Yf9j5orGXrOFdX6UwUVnB8o2OEZ+0GfV0D2QHNVTAu2ohj4QQK6s09RBrZdPNJQ= =QkvS -----END PGP SIGNATURE----- --4Epv4kl9IRBfg3rk--

On Wed, Apr 29, 2015 at 12:04:52PM +0200, David Caro wrote:
On 04/29, Balamurugan Arumugam wrote:
----- Original Message -----
From: "David Caro" <dcaro@redhat.com> To: "Sahina Bose" <sabose@redhat.com> Cc: "Dan Kenigsberg" <danken@redhat.com>, infra@ovirt.org, "Balamurugan Arumugam" <barumuga@redhat.com>, devel@ovirt.org Sent: Wednesday, April 29, 2015 1:38:03 PM Subject: Re: Maintainer rights on vdsm - ovirt-3.5-gluster
You want also push rights? It's not the same submit, push, create reference, verify, code review.
All those are different rights. I've added the submit, code-review and verify rights. Let me know if you want also the rest.
Also note that pushing and submitting is not the same, pushing will skip gerrit and any gerrit checks, so it's usually something to avoid. While submitting is done through gerrit, what allows gerrit to check validity of the code to be merged (gerrit hooks, updating bugzillas, jenkins jobs, signed-by flabs).
The idea behind push right is that we would do periodical rebase of ovirt-3.5-gluster branch with ovirt-3.5 branch. Is this recommended way to do that?
Which kind of rebase? Does it require using --force?
Yes. The expected use case is as such: - Bala merges patches onto his ovirt-3.5-gluster branch via gerrit. - Important patches are merged onto ovirt-3.5 by Yaniv. - Bala wants to have them in ovirt-3.5-gluster - Bala rebases ovirt-3.5-gluster on top of ovirt-3.5 on his host, and pushes the new has as the tip new of ovirt-3.5-gluster. Pleaes let him do that! Dan.

--7lMq7vMTJT4tNk0a Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Done! On 04/29, Dan Kenigsberg wrote: > On Wed, Apr 29, 2015 at 12:04:52PM +0200, David Caro wrote: > > On 04/29, Balamurugan Arumugam wrote: > > >=20 > > >=20 > > > ----- Original Message ----- > > > > From: "David Caro" <dcaro@redhat.com> > > > > To: "Sahina Bose" <sabose@redhat.com> > > > > Cc: "Dan Kenigsberg" <danken@redhat.com>, infra@ovirt.org, "Balamur= ugan Arumugam" <barumuga@redhat.com>, > > > > devel@ovirt.org > > > > Sent: Wednesday, April 29, 2015 1:38:03 PM > > > > Subject: Re: Maintainer rights on vdsm - ovirt-3.5-gluster > > > >=20 > > > > You want also push rights? It's not the same submit, push, create r= eference, > > > > verify, code review. > > > >=20 > > > > All those are different rights. I've added the submit, code-review = and verify > > > > rights. Let me know if you want also the rest. > > > >=20 > > > >=20 > > > > Also note that pushing and submitting is not the same, pushing will= skip > > > > gerrit > > > > and any gerrit checks, so it's usually something to avoid. While su= bmitting > > > > is > > > > done through gerrit, what allows gerrit to check validity of the co= de to be > > > > merged (gerrit hooks, updating bugzillas, jenkins jobs, signed-by f= labs). > > > >=20 > > >=20 > > > The idea behind push right is that we would do periodical rebase of o= virt-3.5-gluster branch with ovirt-3.5 branch. Is this recommended way to = do that? > > >=20 > >=20 > > Which kind of rebase? Does it require using --force? >=20 > Yes. The expected use case is as such: >=20 > - Bala merges patches onto his ovirt-3.5-gluster branch via gerrit. > - Important patches are merged onto ovirt-3.5 by Yaniv. > - Bala wants to have them in ovirt-3.5-gluster > - Bala rebases ovirt-3.5-gluster on top of ovirt-3.5 on his host, and > pushes the new has as the tip new of ovirt-3.5-gluster. >=20 > Pleaes let him do that! >=20 > Dan. --=20 David Caro Red Hat S.L. Continuous Integration Engineer - EMEA ENG Virtualization R&D Tel.: +420 532 294 605 Email: dcaro@redhat.com Web: www.redhat.com RHT Global #: 82-62605 --7lMq7vMTJT4tNk0a Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJVQOJBAAoJEEBxx+HSYmnD2SYIAJaZOxR/j/Gck5S/wLgYOeFu wHLM6qdu0TzcFn/BQ4Ki6MCuCZR3R/JQ1ZhtGia0Pfpo8pstQI4P5iu5bbTIlaWs MpfkdY1irs++HPsF9tWTF45QMmkW8KJbTm6n6jdRJ0lpVt/HGbUkXDg8HN+Ig3vC P3oKnBXb3i9Tn7s4gK55C8ReTGSODYad5tgLGgf2eUZHjwZ8CZWa11JpBdCdrMdx 3EZTzfH1ox+yskCPeQVLd25IXuErJDip2Vc47i9cEXKZPy9ghpX+/XFherFL/Rk0 J5TgPZUI0U+T3RP2uTtpMI5o46OwlMKlNP548ZF3ArLIkwtSJItjkGnNVgHsTXs= =+YAR -----END PGP SIGNATURE----- --7lMq7vMTJT4tNk0a--

--cWoXeonUoKmBZSoM Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Done On 04/20, Dan Kenigsberg wrote:
On Mon, Apr 20, 2015 at 03:20:18PM +0530, Sahina Bose wrote:
Hi! =20 On the vdsm branch "ovirt-3.5-gluster", could you provide merge rights = to Bala (barumuga@redhat.com) ? =20 +1 from me. =20 ovirt-3.5-gluster needs a rebase on top of the current ovirt-3.5
Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
--=20 David Caro Red Hat S.L. Continuous Integration Engineer - EMEA ENG Virtualization R&D Tel.: +420 532 294 605 Email: dcaro@redhat.com Web: www.redhat.com RHT Global #: 82-62605 --cWoXeonUoKmBZSoM Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJVQJBjAAoJEEBxx+HSYmnDmdcH/jaN3VYxBq82KPLc9GjPXBZm AZdd/fFHKCgQNLGBmeUPDsZ6817DJpYegSZTCjZk/bfzDt82sQR4akIm74gjvrPx rY5KFtZ0nu9pyl1BwOFbHw+/kfHJdjftrniaMOVasZfz6bWPFF+aUx1y/P4cIGMP fUo/xrdvwPLkcWfU9SqyBfWZxm03c9JSXxVvJhRdvivSMFFLNXrihQzcoKpBqFki rSvJgrqykQeYRRnxShs4s13/EFhh6DHILEX1bgevYefiGLHVyS0lh4SpV4kuCXLJ bWRX1PNEgA7tR/nv2eQG5N+4QQfe4r/aDfhK2I0AEjAYVS4StHMcJVhT8rzE+pU= =OEjg -----END PGP SIGNATURE----- --cWoXeonUoKmBZSoM--

On Wed, Apr 29, 2015 at 10:03:47AM +0200, David Caro wrote:
Done
On 04/20, Dan Kenigsberg wrote:
On Mon, Apr 20, 2015 at 03:20:18PM +0530, Sahina Bose wrote:
Hi!
On the vdsm branch "ovirt-3.5-gluster", could you provide merge rights to Bala (barumuga@redhat.com) ?
+1 from me.
ovirt-3.5-gluster needs a rebase on top of the current ovirt-3.5
Thanks. Few months have passed, and now we need Sahina herself as an admin of the this branch. Would you please add her as well?

--kvUQC+jR9YzypDnK Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Done! On 11/16 15:28, Dan Kenigsberg wrote:
On Wed, Apr 29, 2015 at 10:03:47AM +0200, David Caro wrote:
Done =20 On 04/20, Dan Kenigsberg wrote:
On Mon, Apr 20, 2015 at 03:20:18PM +0530, Sahina Bose wrote:
Hi! =20 On the vdsm branch "ovirt-3.5-gluster", could you provide merge rig= hts to Bala (barumuga@redhat.com) ? =20 +1 from me. =20 ovirt-3.5-gluster needs a rebase on top of the current ovirt-3.5 =20 Thanks. Few months have passed, and now we need Sahina herself as an admin of the this branch. Would you please add her as well?
--=20 David Caro Red Hat S.L. Continuous Integration Engineer - EMEA ENG Virtualization R&D Tel.: +420 532 294 605 Email: dcaro@redhat.com Web: www.redhat.com RHT Global #: 82-62605 --kvUQC+jR9YzypDnK Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJWSeTKAAoJEEBxx+HSYmnDSwcH/RqlnMJKgd853I/74IqiiV14 mi4GpnER/kb6Bhe/rYTmJIaz6cG9Bn4HUunirAugIGLes9iwfk0J+DVByNfihlr0 9I5ujQEmC8OBBpR1O8WnDO7lpLyM7VVAnonak93zKJdedv8EyCGfM/rrTybVkD3x tW5pjsVcTeSkvjp7EjZAEPss4Xhi0GKLEefVmqLB7/EfSusydASau1QieB5CCRLN 9gBmAy0UtA2wu1lq4qHn69YUSAYwFkvvHka4uf0wIDfUSqVv1iKpw8blP2+NfKaG mBbVtO3VG9Eo02+mqP8LEEReNmKozC9V5yGBfJpxzNV+9eamG3Zs2e2PoUidyek= =a2Rf -----END PGP SIGNATURE----- --kvUQC+jR9YzypDnK--

Thanks! On 11/16/2015 07:44 PM, David Caro wrote:
Done!
On 11/16 15:28, Dan Kenigsberg wrote:
On Wed, Apr 29, 2015 at 10:03:47AM +0200, David Caro wrote:
Done
On 04/20, Dan Kenigsberg wrote:
On Mon, Apr 20, 2015 at 03:20:18PM +0530, Sahina Bose wrote:
Hi!
On the vdsm branch "ovirt-3.5-gluster", could you provide merge rights to Bala (barumuga@redhat.com) ? +1 from me.
ovirt-3.5-gluster needs a rebase on top of the current ovirt-3.5 Thanks. Few months have passed, and now we need Sahina herself as an admin of the this branch. Would you please add her as well?
participants (4)
-
Balamurugan Arumugam
-
Dan Kenigsberg
-
David Caro
-
Sahina Bose