Perfect.

On Wed, Oct 21, 2015 at 9:52 AM, Benedikt Ritter <brit...@apache.org> wrote:

> 2015-10-21 9:42 GMT+02:00 Sergio Fernández <wik...@apache.org>:
>
> > On Wed, Oct 21, 2015 at 9:11 AM, Benedikt Ritter <brit...@apache.org>
> > wrote:
> >
> > > 2015-10-21 9:06 GMT+02:00 Gary Gregory <garydgreg...@gmail.com>:
> > >
> > > > Git must be different from Svn WRT infra. I would log an INFRA ticket
> > so
> > > we
> > > > can find out if this a one-off for Sergio's account or a problem for
> > all
> > > > Commons git repos.
> > >
> > > Good idea, I'll do that. But I'd like to make sure Sergio really can't
> > push
> > > to the repo. Maybe he just hasn't tried because he didn't know that it
> > > works. If there is a problem, I'll talk to infra.
> > >
> >
> > No, I can't:
> >
> > $ git push
> > Password for 'https://wik...@git-wip-us.apache.org':
> > Counting objects: 16, done.
> > Delta compression using up to 4 threads.
> > Compressing objects: 100% (3/3), done.
> > Writing objects: 100% (3/3), 315 bytes | 0 bytes/s, done.
> > Total 3 (delta 2), reused 0 (delta 0)
> > remote: You are not authorized to edit this repository.
> > remote:
> > To https://wik...@git-wip-us.apache.org/repos/asf/commons-lang.git
> >  ! [remote rejected] master -> master (pre-receive hook declined)
> > error: failed to push some refs to '
> > https://wik...@git-wip-us.apache.org/repos/asf/commons-lang.git'
> >
> >
> I've created INFRA-10636 [1].
>
> @Sergio: I won't merge LANG-1175 so that we can use it for testing.
>
> Thank you,
> Benedikt
>
> [1]
> https://issues.apache.org/jira/servicedesk/customer/portal/1/INFRA-10636
>
>
> >
> >
> >
> > --
> > Sergio Fernández
> > Partner Technology Manager
> > Redlink GmbH
> > m: +43 6602747925
> > e: sergio.fernan...@redlink.co
> > w: http://redlink.co
> >
>
>
>
> --
> http://people.apache.org/~britter/
> http://www.systemoutprintln.de/
> http://twitter.com/BenediktRitter
> http://github.com/britter
>



-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Reply via email to