public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Jim Kingdon <kingdon@panix.com>
To: cgf@cygnus.com
Cc: shebs@shebs.cnchost.com, overseers@sources.redhat.com
Subject: Re: [Fwd: failure notice]
Date: Fri, 07 Jul 2000 18:46:00 -0000	[thread overview]
Message-ID: <200007080146.VAA00415@panix6.panix.com> (raw)
Message-ID: <20000707184600.yiY4LiY87pQ_o3lCpW_IERADQMF40sfSlz5DZXdf4xM@z> (raw)
In-Reply-To: <20000707183012.C27406@cygnus.com>

> I just fixed one of these in the cygwin-webpages-cvs mailing list.
> I wonder if some of the other cvs mailing lists are similarly affected.

Ah, *that*'s why one of the outhost files was already updated when I
went to edit them all.  I've updated them all en mase (they were almost
all affected as far as I know).

> I thought it was best to change the contents outhost to *.sources.redhat.com.
> Is that the best way to deal with this for the CVS lists?

Nit: outhost isn't a wildcard, it is a single hostname (it gets put
into the headers in outgoing mail in a few places).  So it is
sources.redhat.com not *.sources.redhat.com.

Changing outhost to sources.redhat.com instead of adding -T to
ezmlm-reject is OK as long as you know that everything which is
sending email has been moved to sources.redhat.com.  If some of the
senders might still be using sourceware.cygnus.com, then the -T (plus
local-mail-only or check-for-listname) solution is how to handle it.

  parent reply	other threads:[~2000-07-07 18:46 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-30  6:08 Stan Shebs
2000-07-07  8:56 ` Stan Shebs
2000-12-30  6:08 ` Jim Kingdon
2000-07-07  9:43   ` Jim Kingdon
2000-12-30  6:08   ` Chris Faylor
2000-07-07 15:30     ` Chris Faylor
2000-12-30  6:08     ` Jim Kingdon [this message]
2000-07-07 18:46       ` Jim Kingdon
2000-12-30  6:08       ` Chris Faylor
2000-07-07 19:05         ` Chris Faylor
  -- strict thread matches above, loose matches on Subject: below --
2007-02-19 21:12 Mark Mitchell
2007-02-19 21:21 ` Christopher Faylor
2007-02-19 22:03   ` Mark Mitchell
2004-08-18 17:20 Corinna Vinschen
2004-08-18 17:44 ` Ian Lance Taylor
2004-08-18 17:54   ` Corinna Vinschen
2004-08-18 18:52     ` Ian Lance Taylor
2004-08-18 22:13       ` Ian Lance Taylor
2004-08-18 22:21       ` Corinna Vinschen
2003-11-17 15:23 Andrew Cagney
2003-11-18  7:48 ` law
2003-11-18 14:40   ` Andrew Cagney
2003-11-18 15:53     ` Matthew Galgoci
2003-11-18 16:18       ` Ian Lance Taylor
2003-11-18 16:28         ` Christopher Faylor
2003-11-18 16:16     ` Christopher Faylor
2003-11-18 16:23       ` Andrew Cagney
2003-11-18 16:33         ` Christopher Faylor
2003-11-18 16:16 ` Ian Lance Taylor
     [not found] <1066412429.25550.133.camel@doubledemon.codesourcery.com>
2003-10-17 17:58 ` root
2003-06-04  4:30 Joern Rennecke
2003-02-01  2:32 Robert Love
2003-02-01  2:53 ` Christopher Faylor
2002-08-16 20:19 Ulrich Drepper
2002-08-16 20:25 ` Christopher Faylor
2002-03-05 12:18 Joel Sherrill
2002-03-07 20:57 ` Andrew Cagney
2001-04-23 11:46 Jonathan Larmour
2001-04-23 11:50 ` Jonathan Larmour
2000-12-30  6:08 Jonathan Larmour
2000-08-30 11:12 ` Jonathan Larmour
2000-12-30  6:08 ` Jason Molenda
2000-08-30 11:32   ` Jason Molenda
2000-12-30  6:08   ` Jason Molenda
2000-08-30 12:03     ` Jason Molenda
2000-12-30  6:08     ` Chris Faylor
2000-08-30 12:37       ` Chris Faylor
2000-12-30  6:08       ` Jason Molenda
2000-08-30 13:15         ` Jason Molenda
2000-12-30  6:08         ` Chris Faylor
2000-08-30 13:45           ` Chris Faylor
2000-12-30  6:08         ` Jonathan Larmour
2000-08-30 13:51           ` Jonathan Larmour
2000-12-30  6:08           ` Chris Faylor
2000-08-30 14:01             ` Chris Faylor
2000-12-30  6:08             ` Jonathan Larmour
2000-08-30 14:13               ` Jonathan Larmour

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=200007080146.VAA00415@panix6.panix.com \
    --to=kingdon@panix.com \
    --cc=cgf@cygnus.com \
    --cc=overseers@sources.redhat.com \
    --cc=shebs@shebs.cnchost.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.
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).