Hi Roger,
only downside of enabling *all* repositories is:
- Note: If you're adding
all of your code repos to Gerrit, you will lose control of the
'container' for your project(/gitroot/projectname), as
Webmaster will give the container to the Gerrit user. This
means that you will not be able to create new repos via the
initrepo command, instead you will have to contact
Webmaster(via a bug).
which is one reason we didn't do it immediately.
Also note we chose option 2:
- I want project committers to
be able to bypass the Gerrit code review system and push
changes directly to the git repo. Please note that
this will have to be done via the 'new' Gerrit URLs(SSH and
HTTPS). The original dev.eclipse.org SSH URLs will become
inactive once Gerrit is enabled.
Ian
On 06/12/13 23:10, Roger Light wrote:
Hi all,
I'd like to submit a bug requesting Gerrit for the Python client, but
was wondering if I should ask for all of our remaining repositories to
be enabled? I think if it makes life easier for people to contribute
then it is something that we should support across the whole project.
Cheers,
Roger
On Tue, Dec 3, 2013 at 3:57 PM, Ian Craggs
<icraggs@xxxxxxxxxxxxxxxxxxxxxxx> wrote:
Hi All,
Gerrit has been enabled for the Java and C repositories
(https://bugs.eclipse.org/bugs/show_bug.cgi?id=422785):
- org.eclipse.paho.mqtt.java.git
- org.eclipse.paho.mqtt.c.git
"Committers will need to update their Git URLs to point to the new Gerrit
ones. For more details see the wiki http://wiki.eclipse.org/Gerrit"
We are hoping that this will make contributing, and the handling of
contributions, easier.
Ian
_______________________________________________
paho-dev mailing list
paho-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/paho-dev
_______________________________________________
paho-dev mailing list
paho-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/paho-dev
|