On Wednesday, 21 January 2015 23:12:33 CEST, Thomas L=C3=BCbking wrote:
> The bug cooked up for asking google about gerrit and scratch repos.
> The problem is that pushing into any branch would close a=20
> review - I can only assume it was linked in the mail thread I=20
> found because a similar issue would affect clones etc. (ie.=20
> likely when the change-id gets pushed anywhere)
>
> My uninformed guess would be to handle the change-id smarter,=20
> ie. bind it to a branch (and pot. repo)

IMHO, a pretty straightforward option is to close bugzilla entries once a=20
change is approved and lands in an appropriate branch, and that's easy with=20=

Gerrit's its-bugzilla plugin. It is possible to specify which branches are=20=

appropriate, of course.

> Thanks - looks actually nice (and supports dumb diffs ;-)
> Sicne I've no mediawiki account: do you know whether it already=20
> allows ppl. to access (all) "their" patches w/o modifications=20
> (ie. like the RB dashboard) as well?

Yes. Their instance doesn't keep a "secondary index" which limits=20
searching, but a proper query would be something like=20
"owner:you@example.org OR comment:'uploaded by you@example.org'". That=20
works on our Gerrit.

Jan

--=20
Trojit=C3=A1, a fast Qt IMAP e-mail client -- http://trojita.flaska.net/