From: Bastien <bastien.guerry@wikimedia.fr>
To: Achim Gratz <Stromeko@nexgo.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: [Worg] some issues
Date: Mon, 17 Jan 2011 21:10:03 +0100 [thread overview]
Message-ID: <8739or1eck.fsf@gnu.org> (raw)
In-Reply-To: <87oc7fuxvi.fsf@Rainer.invalid> (Achim Gratz's message of "Mon, 17 Jan 2011 20:35:29 +0100")
Achim Gratz <Stromeko@nexgo.de> writes:
> Matt Lundin <mdl@imapmail.org> writes:
> [...]
>
> Bastien mentioned requesting push access to Worg from you... I've
> actually created an SSH key on repo.or.cz for this a while back (but
> never requested push access to Worg), how does this work on the new
> Worg?
Worg hasn't been migrated to the new server, yet: pushing from your
Worg clone should work as usual.
As Jason said, there is a plan to migrate Worg.git to the new server but
it's a bigger move than migrating org-mode.git since there are many more
people involved.
As everyone can see, I'm still catching up with old emails/requests and
I don't want to migrate Worg before I've found my maintainance "rhythm"!
So please bare with me on this.
Thanks!
> I keep this question on the orgmode list since the answer will
> probably be of interest to other would-be-Worgers.
PS: The process of migrating requires Worgers to send me their public
key: so if would-be-Worgers don't mind to send it twice, they can open
an account on repo.or.cz... otherwise, they can safely submit patches.
--
Bastien
next prev parent reply other threads:[~2011-01-17 20:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-16 12:32 [Worg] some issues Achim Gratz
2011-01-16 19:24 ` Matt Lundin
2011-01-17 19:35 ` Achim Gratz
2011-01-17 20:10 ` Bastien [this message]
2011-01-18 4:55 ` Matt Lundin
2011-01-17 17:46 ` Jason Dunsmore
2011-01-17 17:48 ` Bastien
2011-01-17 19:10 ` Achim Gratz
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=8739or1eck.fsf@gnu.org \
--to=bastien.guerry@wikimedia.fr \
--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).