all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Carsten Dominik <dominik@uva.nl>
To: Bastien <bzg@gnu.org>
Cc: org-mode list <emacs-orgmode@gnu.org>
Subject: Re: Push rights for repository
Date: Fri, 5 May 2017 12:01:54 +0200	[thread overview]
Message-ID: <CADn3Z2JzLXGD48_JrGx5=wRC8hPhsJqRkUvVfe8KbbApgnNmhQ@mail.gmail.com> (raw)
In-Reply-To: <87bmr7wtie.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1067 bytes --]

Thank you Bastien,

indeed, it is fixed now - apparently I had cloned with

    $ git clone git://orgmode.org/org-mode.git

instead of

    $ git clone orgmode@orgmode.org:org-mode.git

- Carsten


On Fri, May 5, 2017 at 11:19 AM, Bastien <bzg@gnu.org> wrote:

> Hi Carsten,
>
> Carsten Dominik <dominik@uva.nl> writes:
>
> > I seem to have lost my push privilege to the git repository.  Does
> > anyone know why that might be the case?
> >
> > $ git remote -v shows
> >
> >     origin git://orgmode.org/org-mode.git (fetch)
> >     origin git://orgmode.org/org-mode.git (push)
>
> I get
>
> origin  orgmode@orgmode.org:org-mode.git (fetch)
> origin  orgmode@orgmode.org:org-mode.git (push)
>
> It looks like you are trying to push from a read-only repo?
>
> > and I believe that my ssh settings are OK - I did push a few weeks
> > ago successfully.  Still, on a push attempt, I get
> >
> >       fatal: remote error: access denied or repository not exported:
> > /org-mode.git
>
> I confirm your key didn't change on the server.
>
> Let me know!
>
> --
>  Bastien
>

[-- Attachment #2: Type: text/html, Size: 2011 bytes --]

      reply	other threads:[~2017-05-05 10:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-05  7:24 Push rights for repository Carsten Dominik
2017-05-05  9:19 ` Bastien
2017-05-05 10:01   ` Carsten Dominik [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='CADn3Z2JzLXGD48_JrGx5=wRC8hPhsJqRkUvVfe8KbbApgnNmhQ@mail.gmail.com' \
    --to=dominik@uva.nl \
    --cc=bzg@gnu.org \
    --cc=emacs-orgmode@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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.