From: Simon Josefsson <jas@extundo.com>
Cc: savannah-hackers@gnu.org, cvs-hackers@gnu.org, sysadmin@gnu.org,
rms@gnu.org, emacs-devel@gnu.org
Subject: Re: emacs arch archive
Date: Fri, 01 Aug 2003 12:54:57 +0200 [thread overview]
Message-ID: <iluy8ydhcla.fsf@latte.josefsson.org> (raw)
In-Reply-To: <buon0eujb93.fsf@mcspd15.ucom.lsi.nec.co.jp> (Miles Bader's message of "01 Aug 2003 12:40:56 +0900")
Miles Bader <miles@lsi.nec.co.jp> writes:
> Richard Stallman <rms@gnu.org> writes:
>> I still don't know how I can provide external access though
>> (alpha.gnu.org used to be suitable for this kind of thing, as it
>> used a directory on fencepost, but I have no idea where it is
>> these days, or how to get write access to it).
>>
>> It is probably the directory ~ftp on fencepost.
>
> It used to be that, but now ~ftp seems to point to something random
> (it only contains two subdirectories `incoming' and `outgoing', but that
> doesn't resemble what's visible on alpha.gnu.org).
>
> There's also /gnu/alpha on fencepost, which _appears_ to contains an the
> old version of ~ftp, but it's not the same as what I see at
> alpha.gnu.org -- it looks like maybe the current alpha was at somepoint
> cloned from what's in /gnu/alpha, but it's apparently diverged quite a
> bit since then.
The GNU Maintenance manual is incorrect about fencepost:~ftp, I sent a
note about this earlier.
The current location for alpha.gnu.org FTP appear to be
gnuftp.gnu.org:~alpha/gnu/.
next prev parent reply other threads:[~2003-08-01 10:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-28 23:19 emacs arch archive Miles Bader
2003-07-30 8:34 ` Miles Bader
2003-07-31 20:01 ` [Savannah-hackers] " Rudy Gevaert
2003-08-01 2:20 ` Richard Stallman
2003-08-01 3:40 ` Miles Bader
2003-08-01 10:54 ` Simon Josefsson [this message]
2003-08-01 3:49 ` Miles Bader
2003-08-09 3:44 ` Miles Bader
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=iluy8ydhcla.fsf@latte.josefsson.org \
--to=jas@extundo.com \
--cc=cvs-hackers@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rms@gnu.org \
--cc=savannah-hackers@gnu.org \
--cc=sysadmin@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.