From: Marcin Borkowski <mbork@mbork.pl>
To: Phillip Lord <phillip.lord@russet.org.uk>
Cc: John Wiegley <jwiegley@gmail.com>,
Emacs developers <emacs-devel@gnu.org>
Subject: Re: Request for write permissions
Date: Wed, 29 Mar 2017 08:20:43 +0200 [thread overview]
Message-ID: <87wpb8ob7o.fsf@jane> (raw)
In-Reply-To: <e949e750f3e99450d57630f9c51324dc.squirrel@cloud103.planethippo.com>
On 2017-03-28, at 14:50, Phillip Lord <phillip.lord@russet.org.uk> wrote:
> On Tue, March 28, 2017 12:29 pm, Marcin Borkowski wrote:
>
>> Thanks. I got the email telling me that I was granted the permissions,
>> however, it seems I cannot push. Here's what I did (using Magit):
>>
>> git push -v origin fix-21072-patch:refs/heads/fix-21072-patch
>>
>> Pushing to git://git.savannah.gnu.org/emacs.git
>> Looking up git.savannah.gnu.org ... done.
>> Connecting to git.savannah.gnu.org (port 9418) ... 208.118.235.201 done.
>> fatal: remote error: access denied or repository not exported: /emacs.git
>>
>>
>> Am I doing something wrong?
>
> git clone <membername>@git.sv.gnu.org:/srv/git/emacs.git
I see. Of course, this is not too convenient for me, since I have a bit
of work in my local repo already. (And not only branches, which I could
fetch easily, but also stashes - they could be fetched, too, but with
more work.)
Thanks anyway,
--
Marcin Borkowski
next prev parent reply other threads:[~2017-03-29 6:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-08 6:39 Request for write permissions Marcin Borkowski
2017-03-09 4:15 ` John Wiegley
2017-03-10 6:17 ` Marcin Borkowski
2017-03-28 12:29 ` Marcin Borkowski
2017-03-28 12:50 ` Phillip Lord
2017-03-28 13:03 ` Andreas Schwab
2017-03-28 15:04 ` Stefan Monnier
2017-03-28 15:35 ` Andreas Schwab
2017-03-29 6:27 ` Marcin Borkowski
2017-03-29 6:23 ` Marcin Borkowski
2017-03-29 6:21 ` Marcin Borkowski
2017-03-29 8:41 ` Andreas Schwab
2017-03-29 6:20 ` Marcin Borkowski [this message]
2017-03-09 9:46 ` Andreas Schwab
2017-03-10 6:17 ` Marcin Borkowski
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wpb8ob7o.fsf@jane \
--to=mbork@mbork.pl \
--cc=emacs-devel@gnu.org \
--cc=jwiegley@gmail.com \
--cc=phillip.lord@russet.org.uk \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).