2011/9/7 Paul Sokolovsky :
> Hello Edwin,
>
> On Tue, 6 Sep 2011 15:52:49 +0200
> Edwin Kempin wrote:
>
>> Hi Paul,
>>
>> I'm afraid that regular expressions are broken in Gerrit 2.2.1, see
>> issue 1015 [1]. It was fixed with commit
>> 9161c709eefc0828a8af4d46f6e8409c307aea1e for Gerrit 2.2.2
>>
Hello Edwin,
On Tue, 6 Sep 2011 15:52:49 +0200
Edwin Kempin wrote:
> Hi Paul,
>
> I'm afraid that regular expressions are broken in Gerrit 2.2.1, see
> issue 1015 [1]. It was fixed with commit
> 9161c709eefc0828a8af4d46f6e8409c307aea1e for Gerrit 2.2.2
> The correct syntax for your case would b
Hi Paul,
I'm afraid that regular expressions are broken in Gerrit 2.2.1, see
issue 1015 [1]. It was fixed with commit
9161c709eefc0828a8af4d46f6e8409c307aea1e for Gerrit 2.2.2
The correct syntax for your case would be "^refs/heads/linaro.*". This
syntax is accepted by Gerrit 2.1.8 and current Gerr
Hello,
We're elaborating our Linaro Gerrit (2.2.1) set up, and would like to
enforce separation between upstream and "our" branches, to disallow
stray commits to upstream branches and keep them pullable from AOSP.
So, we'd like to limit review requests, pushes, etc. to
"refs/heads/for/linaro*" and
