From: Glenn Morris <rgm@gnu.org>
To: merlyn@stonehenge.com (Randal L. Schwartz)
Cc: emacs-devel@gnu.org
Subject: Re: no Savannah bzr/git access this coming Wednesday
Date: Tue, 03 Jun 2014 16:52:35 -0400 [thread overview]
Message-ID: <k61tv5d8bw.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <86bnu9ivbt.fsf@red.stonehenge.com> (Randal L. Schwartz's message of "Tue, 03 Jun 2014 13:36:54 -0700")
You will find the answer to your super-important question at
http://lists.gnu.org/archive/html/savannah-users/2014-05/msg00002.html
prev parent reply other threads:[~2014-06-03 20:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-12 16:10 no Savannah bzr/git access this coming Wednesday Glenn Morris
2014-06-03 20:36 ` Randal L. Schwartz
2014-06-03 20:52 ` Glenn Morris [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
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=k61tv5d8bw.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=merlyn@stonehenge.com \
/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).