From: Andrew Pinski <pinskia@gcc.gnu.org>
To: Kelvin Nilsen <kdnilsen@linux.vnet.ibm.com>
Cc: "Frank Ch. Eigler" <fche@redhat.com>,
"overseers@sourceware.org" <overseers@sourceware.org>
Subject: Re: Getting write access to the gcc repository
Date: Tue, 27 Oct 2015 16:38:00 -0000 [thread overview]
Message-ID: <CA+=Sn1mApouhME+j-BABxc_1DKVwrt5wTXMxk-Hy4QSJxKVeww@mail.gmail.com> (raw)
In-Reply-To: <562952F5.5050703@linux.vnet.ibm.com>
On Fri, Oct 23, 2015 at 5:19 AM, Kelvin Nilsen
<kdnilsen@linux.vnet.ibm.com> wrote:
> So should that give me write access? I'm getting error messages when I try
> to create a branch. I was assuming this was because I did not have write
> authorization. Do you have access to any log files that would help explain
> why this operation is failing?
Because you are using svn instead of svn+ssh to do the copy.
Thanks,
Andrew
>
> Thanks.
>
> kelvin@genoa:~/gcc$ svn copy svn://gcc.gnu.org/svn/gcc/trunk
> svn://gcc.gnu.org/svn/gcc/branches/ibm/kelvin-1
> svn: E170001: Authorization failed
> svn: E170001: Your commit message was left in a temporary file:
> svn: E170001: 'svn-commit.5.tmp'
> kelvin@genoa:~/gcc$
>
>
>
> On 10/22/2015 01:54 PM, Frank Ch. Eigler wrote:
>>
>> Hi -
>>
>>> [...]
>>> What I seem to be missing at the moment is authorization to write to the
>>> svn repository. Will you please help set this up for me?
>>
>> You are already a member of the "gcc" group.
>>
>> - FChE
>>
>
prev parent reply other threads:[~2015-10-23 7:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-22 19:54 Kelvin Nilsen
2015-10-22 21:19 ` Frank Ch. Eigler
2015-10-23 7:11 ` Kelvin Nilsen
2015-10-27 16:38 ` Andrew Pinski [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CA+=Sn1mApouhME+j-BABxc_1DKVwrt5wTXMxk-Hy4QSJxKVeww@mail.gmail.com' \
--to=pinskia@gcc.gnu.org \
--cc=fche@redhat.com \
--cc=kdnilsen@linux.vnet.ibm.com \
--cc=overseers@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).