[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Making your project more openŠhowto enable Gerrit

On 07/10/13 09:51 AM, John Arthorne wrote:
Doug Schaefer <dschaefer@xxxxxxx> wrote on 10/04/2013 06:47:08 PM:

> No they're not. I can't see any way that patches in bugzilla are easier
> than gerrit. It's one "Push to Gerrit" and one "Publish and Submit" clicks
> away from getting a contribution made and accepted.

The "Submit" button is a bit dangerous that way. For most changes you can't thoroughly review it without trying it out, which means loading it into your local workspace. For a bugzilla patch you can paste it directly into the navigator so it really can't be beat (about four keystrokes for the whole process to copy/paste the patch). Whether you use UI or command line, Gerrit is a bit more work there.

I've been meaning to write something up about this but haven't had the time. If you use the commandline there's a handy python script [1] that makes the Gerrit experience a little easier.

The gist of it is that it's a bunch of shortcuts to working with the Gerrit workflow. For example "git review -d <change#>" will pull down a change and create a local branch for it automatically. No more copy/pasting the long commands that Gerrit provides.

Maybe something similar can be integrated into Egit?

[1] https://pypi.python.org/pypi/git-review