From: Kaushal Modi <kaushal.modi@gmail.com>
To: Achim Gratz <Stromeko@nexgo.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: [IMPORTANT] Server migration: please update your git repositories before 31/12/2017
Date: Thu, 04 Jan 2018 18:44:15 +0000 [thread overview]
Message-ID: <CAFyQvY0HiO5L77irsdGwo7Jx3OUF2g0pg2H47o8Amhg6sCY3Kg@mail.gmail.com> (raw)
In-Reply-To: <87zi5t8pfn.fsf@Rainer.invalid>
[-- Attachment #1: Type: text/plain, Size: 1168 bytes --]
On Thu, Jan 4, 2018 at 1:16 PM Achim Gratz <Stromeko@nexgo.de> wrote:
> Bastien Guerry writes:
> >> ~$ git clone git@code.orgmode.org:bzg/org-mode.git
> > ^^^
> >
> > This is for when you have an account on code.orgmode.org and want
> > to clone through ssh.
>
> Have the existing SSH keys been migrated to the new server? Trying to
> clone through this method keeps asking me for a password.
>
No, the keys didn't transfer. As Bastien mentioned in the original email,
you need to create an account on code.orgmode.org first (pasted the
instructions below):
For Org and Worg COMMITTERS
============================
You will need to create a new user on https://code.orgmode.org in
order to push commits to org-mode.git or worg.git:
1. Create a user on https://code.orgmode.org
2. Add your ssh public key
3. Send me an email to be added as a collaborator on Org/Worg
BTW @Nicolas, Bastien: Do these instructions need to go somewhere in the
Org manual too, or Worg? (and as I was framing this question, found that
the Worg also needs to be updated.. it still refers to the old clone URL:
https://orgmode.org/worg/dev/index.html
--
Kaushal Modi
[-- Attachment #2: Type: text/html, Size: 2166 bytes --]
next prev parent reply other threads:[~2018-01-04 18:44 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-28 17:12 [IMPORTANT] Server migration: please update your git repositories before 31/12/2017 Bastien Guerry
2017-12-29 7:32 ` Michael Welle
2017-12-29 12:23 ` Bastien Guerry
2017-12-29 9:59 ` Achim Gratz
2017-12-29 12:26 ` Bastien Guerry
2017-12-30 10:39 ` Allen Li
2017-12-30 11:23 ` Bastien
2017-12-30 11:39 ` Achim Gratz
2017-12-30 11:57 ` Bastien
2017-12-30 21:50 ` Allen Li
2017-12-31 8:53 ` Achim Gratz
2017-12-29 16:43 ` Bastien Guerry
2018-01-04 18:11 ` Achim Gratz
2018-01-04 18:44 ` Kaushal Modi [this message]
2018-01-04 18:50 ` Nicolas Goaziou
2018-01-04 18:52 ` Kaushal Modi
2018-01-05 17:31 ` Kaushal Modi
2018-01-05 17:47 ` Probably broke the Worg build? (Was: Re: [IMPORTANT] Server migration..) Kaushal Modi
2018-01-06 1:54 ` Probably broke the Worg build? Bastien
2018-01-06 2:05 ` Kaushal Modi
2018-01-06 2:54 ` Kaushal Modi
2018-01-04 19:21 ` [IMPORTANT] Server migration: please update your git repositories before 31/12/2017 Achim Gratz
2018-01-04 14:19 ` Kaushal Modi
2018-01-04 15:36 ` Nicolas Goaziou
2018-01-04 16:05 ` Kaushal Modi
2018-01-04 18:12 ` Nicolas Goaziou
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAFyQvY0HiO5L77irsdGwo7Jx3OUF2g0pg2H47o8Amhg6sCY3Kg@mail.gmail.com \
--to=kaushal.modi@gmail.com \
--cc=Stromeko@nexgo.de \
--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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.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).