From: Paul Eggert <eggert@cs.ucla.edu>
To: emacs-devel@gnu.org
Subject: Re: bzr problem
Date: Mon, 27 Feb 2012 14:31:24 -0800 [thread overview]
Message-ID: <4F4C043C.1000601@cs.ucla.edu> (raw)
In-Reply-To: <874nucorks.fsf@gnu.org>
On 02/27/2012 02:10 PM, Sam Steingold wrote:
> what's up?
It's a site-wide problem at Savannah; it's
not limited to bzr, or to Emacs.
Here's the service request for this.
https://savannah.gnu.org/support/index.php?107969
next prev parent reply other threads:[~2012-02-27 22:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-27 22:10 bzr problem Sam Steingold
2012-02-27 22:31 ` Paul Eggert [this message]
2012-02-27 22:36 ` chad
2012-02-27 22:50 ` Andreas Schwab
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=4F4C043C.1000601@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=emacs-devel@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.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).