thanks just what I was looking for.
Had hoped this was more easily runnable but that can be fixed ;)
/max
Max, and others,
The links I gave point to the new reports ... if you navigate to the
top most page of the reports,
There are really two scenarios for using Gerrit - at least for me:
1) I know I want to commit that fix but want it to be verified by Hudson
first.
2) I or a contributor uploads some code for a real review by another
committer. In that case it would be very bad if the change got merged
after
I know I am coming very late to the Gerrit usage „party“ in the simrel. So I am
now biten by all the obstacles you have to overcome to be able to contribute
again.
To me the two scenarios below are descriptions of
1. You want to push to Git directly because you know what you are doing (and
I am sorry for that…. I should have said „previous style“…
Still I dont get it why I cant directly push to Git and rather push to
Gerrit which immediatelly pushes to Git ? Is that extra route a benefit
for anyone. I would prefer a „model“ („style ? Whatever) where committers
can push to Git and
I rather want the old style before Gerrit back (but then maybe I am alone in
this) and then we use Gerrit for contributions which need to be reviewed.
This is not old-style, it's exactly the current behaviour for most Eclipse
projects using Gerrit, including Simrel. Just the URL of push has
cross-project-issues-dev-boun...@eclipse.org wrote on 05/21/2015 03:26:36
AM:
From: Max Rydahl Andersen mande...@redhat.com
To: Cross project issues cross-project-issues-dev@eclipse.org,
Date: 05/21/2015 05:28 AM
Subject: Re: [cross-project-issues-dev] New reports for versioning.
Sent by:
On 05/21/2015 07:09 AM, Christian Campo wrote:
Still I dont get it why I cant directly push to Git and rather push to
Gerrit which immediatelly pushes to Git ?
Gerrit == Git
One of them is written in C
The other is written in Java.
They both do the exact same thing.
One of them has a
I think what people trip over, as I did, is that Gerrit is two independent
things:
1- a code review tool
2- a git portal that can be treated as a normal git remote. This one has
nothing to do with code reviews and provides the same abilities as direct git
(and more).
Marc
-Original
Hi,
With the Eclipse Installer it's now very easy to create or update a workspace with all the things you need for Simrel
contributions. If you want to give it a try:
1) Make sure you've got a Gerrit account:
http://wiki.eclipse.org/Gerrit#User_Account
2) I find SSH keys convenient:
