Re: Different Gerrit workflows -- was Master branch now requires liborcus 0.5.0 or higher.

2013-04-24 Thread d . ostrovsky
Quoting Norbert Thiebaud : On Wed, Apr 24, 2013 at 2:02 AM, David Ostrovsky wrote: On Tue Apr 23 18:19:55 PDT 2013, Norbert Thiebaud wrote: If you think that that list is missing someone(s) that are very present on IRC and could help cover the request, I'm all ears. can you please add Steph

Re: Different Gerrit workflows -- was Master branch now requires liborcus 0.5.0 or higher.

2013-04-24 Thread Norbert Thiebaud
On Wed, Apr 24, 2013 at 2:02 AM, David Ostrovsky wrote: > On Tue Apr 23 18:19:55 PDT 2013, Norbert Thiebaud wrote: > >>If you think that that list is missing someone(s) that are >>very present on IRC and could help cover the request, I'm all ears. > can you please add Stephan and Lionel? I have n

Re: Different Gerrit workflows -- was Master branch now requires liborcus 0.5.0 or higher.

2013-04-23 Thread David Ostrovsky
On Tue Apr 23 18:19:55 PDT 2013, Norbert Thiebaud wrote: >If you think that that list is missing someone(s) that are >very present on IRC and could help cover the request, I'm all ears. can you please add Stephan and Lionel? >but adding 200 peoples to that list is not something I consider viable

Re: Different Gerrit workflows -- was Master branch now requires liborcus 0.5.0 or higher.

2013-04-23 Thread Norbert Thiebaud
On Tue, Apr 23, 2013 at 4:49 PM, Bjoern Michaelsen wrote: > I see you contemplating about integrating it in the UI and semi-automatic > triggering, but how is that blocking enabling it I see to allow committers do > to manual triggering via ssh (after checking the queue). What am I missing? You

Re: Different Gerrit workflows -- was Master branch now requires liborcus 0.5.0 or higher.

2013-04-23 Thread Bjoern Michaelsen
On Tue, Apr 23, 2013 at 11:21:07AM -0500, Norbert Thiebaud wrote: > On Tue, Apr 23, 2013 at 9:07 AM, Bjoern Michaelsen > wrote: > > > > with so far no arguments against it. Lets make the decision on the ESC call. > > Really ? Have I been too diplomatic about it ? Seems so ;) I see you contempla

Re: Different Gerrit workflows -- was Master branch now requires liborcus 0.5.0 or higher.

2013-04-23 Thread Norbert Thiebaud
On Tue, Apr 23, 2013 at 9:07 AM, Bjoern Michaelsen wrote: > > with so far no arguments against it. Lets make the decision on the ESC call. Really ? Have I been too diplomatic about it ? Norbert ___ LibreOffice mailing list LibreOffice@lists.freedesktop

Re: Different Gerrit workflows -- was Master branch now requires liborcus 0.5.0 or higher.

2013-04-23 Thread Bjoern Michaelsen
On Tue, Apr 23, 2013 at 02:43:20PM +0200, Stephan Bergmann wrote: > On 04/21/2013 01:04 PM, David Ostrovsky wrote: > >So back to your use case: the content of your feature branch can be put > >on Gerrit for *only* verification (not wasting days or weeks but only 2 > >hours) with *one* command: > >g

Different Gerrit workflows

2013-04-23 Thread d . ostrovsky
On Tue Apr 23 05:43:20 PDT 2013, Stephan Bergmann wrote: On 04/21/2013 01:04 PM, David Ostrovsky wrote: So back to your use case: the content of your feature branch can be put on Gerrit for *only* verification (not wasting days or weeks but only 2 hours) with *one* command: git push logerrit :r

Re: Different Gerrit workflows -- was Master branch now requires liborcus 0.5.0 or higher.

2013-04-23 Thread Stephan Bergmann
On 04/21/2013 01:04 PM, David Ostrovsky wrote: So back to your use case: the content of your feature branch can be put on Gerrit for *only* verification (not wasting days or weeks but only 2 hours) with *one* command: git push logerrit :refs/for/master But that does not trigger the actual verif

Different Gerrit workflows -- was Master branch now requires liborcus 0.5.0 or higher.

2013-04-21 Thread David Ostrovsky
On Tue Apr 16 09:32:13 PDT 2013, Kohei Yoshida wrote: >>On Sat, Apr 13, 2013 at 5:55 AM, Bjoern Michaelsen < >>bjoern.michaelsen at canonical.com> wrote: >> >> BTW, this seems like a prime example benefitting from "upload to gerrit, >> let >> someone schudule a test build on all platforms" -- an