From: Jeffrey A Law <law@redhat.com>
To: Christopher Faylor <cgf@redhat.com>
Cc: "Joseph S. Myers" <jsm28@cam.ac.uk>, overseers@gcc.gnu.org
Subject: Re: libstdc++ list still thinks it's at sources.redhat.com
Date: Wed, 03 Jan 2001 20:57:00 -0000 [thread overview]
Message-ID: <8991.978581867@upchuck> (raw)
Message-ID: <20010103205700.ypfEczvv11IW26Ll7dkB2ghQCQqczE7zyUNpmmbRiFA@z> (raw)
In-Reply-To: <20010103140748.B14748@redhat.com>
In message < 20010103140748.B14748@redhat.com >you write:
> On Wed, Jan 03, 2001 at 07:04:07PM +0000, Joseph S. Myers wrote:
> >On Mon, 1 Jan 2001, Christopher Faylor wrote:
> >> I assume that all gcc.gnu.org lists are similar, though.
> >
> >No, the messages produced by gcc-subscribe (for example) use
> >gcc.gnu.org throughout.
>
> Ok. It looks like the list really needs to be physically moved from
> sourceware to the gcc ezmlm hierarchy, then.
BTW, the physical location is pretty easy to change. The easiest
way to do it without interrupting service is to mv the directory into
the new location and leave a symlink temporarily in place.
Then you go to /qmail/alias and update it's links to point to the new
location.
Then you go back and zap the old directory symlink.
This avoids most problems with interruption of service.
I'll try to take care physically moving the libstdc++ shortly.
jeff
next prev parent reply other threads:[~2001-01-03 20:57 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-31 19:40 Joseph S. Myers
2001-01-01 11:49 ` Joseph S. Myers
2001-12-31 19:40 ` Gerald Pfeifer
2001-01-01 12:16 ` Gerald Pfeifer
2001-12-31 19:40 ` Joseph S. Myers
2001-01-03 11:09 ` Joseph S. Myers
2001-12-31 19:40 ` Benjamin Kosnik
2001-01-03 11:18 ` Benjamin Kosnik
2001-12-31 19:40 ` Jeffrey A Law
2001-01-03 12:21 ` Jeffrey A Law
2001-12-31 19:40 ` Benjamin Kosnik
2001-01-03 12:37 ` Benjamin Kosnik
2001-12-31 19:40 ` Jason Molenda
2001-01-03 13:35 ` Jason Molenda
2001-12-31 19:40 ` Phil Edwards
2001-01-03 11:20 ` Phil Edwards
2001-12-31 19:40 ` Christopher Faylor
2001-01-01 12:03 ` Christopher Faylor
2001-12-31 19:40 ` Joseph S. Myers
2001-01-03 11:04 ` Joseph S. Myers
2001-12-31 19:40 ` Christopher Faylor
2001-01-03 11:07 ` Christopher Faylor
2001-12-31 19:40 ` Jeffrey A Law [this message]
2001-01-03 20:57 ` Jeffrey A Law
2001-12-31 19:40 ` Jeffrey A Law
2001-01-03 21:34 ` Jeffrey A Law
2001-12-31 19:40 ` Jeffrey A Law
2001-01-03 12:24 ` Jeffrey A Law
2001-12-31 19:40 ` Jeffrey A Law
2001-01-03 12:26 ` Jeffrey A Law
2001-12-31 19:40 ` Joseph S. Myers
2001-01-03 12:34 ` Joseph S. Myers
2001-12-31 19:40 ` Christopher Faylor
2001-01-03 12:56 ` Christopher Faylor
2001-12-31 19:40 ` Joseph S. Myers
2001-01-03 13:04 ` Joseph S. Myers
2001-12-31 19:40 ` Christopher Faylor
2001-01-03 14:06 ` Christopher Faylor
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=8991.978581867@upchuck \
--to=law@redhat.com \
--cc=cgf@redhat.com \
--cc=jsm28@cam.ac.uk \
--cc=overseers@gcc.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.
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).