From: "Frank Ch. Eigler" <fche@elastic.org>
To: ben narwal <ben.narwal@outlook.com>
Cc: "overseers@gcc.gnu.org" <overseers@gcc.gnu.org>
Subject: Re: Question about write-access svn repository of my account
Date: Sat, 20 Apr 2019 10:59:00 -0000 [thread overview]
Message-ID: <20190420105945.GA532812@elastic.org> (raw)
In-Reply-To: <HK0PR02MB2897F2F9F6873F594C4B42AE9C200@HK0PR02MB2897.apcprd02.prod.outlook.com>
Hi -
> [...]
> Recently I ran into problem in accessing write-access svn repository
(You didn't identify the problem.)
> while read-only access is fine with below command line: svn checkout
> svn://gcc.gnu.org/svn/gcc/trunk SomeLocalDir
> Also I didn't made any change to either svn or ssh configuration, so
> could you help me check if the public key is still registered
> correctly to my account please? Thanks very much for your time.
The key looks fine, as does your account. You will need to use
svn+ssh://.. svn urls to get write access.
- FChE
next prev parent reply other threads:[~2019-04-20 10:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-20 10:11 ben narwal
2019-04-20 10:59 ` Frank Ch. Eigler [this message]
2019-04-20 15:42 ` Christopher Faylor
2019-04-22 14:27 ` ben narwal
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=20190420105945.GA532812@elastic.org \
--to=fche@elastic.org \
--cc=ben.narwal@outlook.com \
--cc=overseers@gcc.gnu.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).