public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Chris Faylor <cgf@cygnus.com>
To: Jonathan Larmour <jlarmour@redhat.com>
Cc: Jason Molenda <jason-swarelist@molenda.com>,
	overseers@sources.redhat.com
Subject: Re: [Fwd: failure notice]
Date: Sat, 30 Dec 2000 06:08:00 -0000	[thread overview]
Message-ID: <20000830170040.A28076@cygnus.com> (raw)
In-Reply-To: <39AD73E6.5A848A10@redhat.com>

On Wed, Aug 30, 2000 at 09:51:50PM +0100, Jonathan Larmour wrote:
>Looking at check-for-listname.sh (thanks for the pointer Crash), the
>relevant line is:
>if cat $TMPFILE | sed -n '/^[Cc][Cc]: /,/^[a-zA-Z]/p' | sed '$d' |
>   egrep -i "$VALID_LISTNAME" >/dev/null 2>&1                     
>
>If the "sed '$d' |" is removed, it works correctly on this mail. I can't
>see any reason for the "sed '$d'" to be there. Is there one? If not, I'll
>just remove it.

I think that the $d guards against something like:

To: greatopportunities@foryou.com,
    dontmiss@this.com
Subject: ecos-discuss@sourceware.cygnus.com

Admittedly, it's not likely that something like this would happen, but this
should be moot anyway.  I've checked in a patch which should solve this problem.

I've checked it on the header in question and it seems to work fine.

Now, let's see if there are thousands of angry screams when we find that this
only works for ecos-discuss@sourceware.cygnus.com...

cgf

WARNING: multiple messages have this Message-ID
From: Chris Faylor <cgf@cygnus.com>
To: Jonathan Larmour <jlarmour@redhat.com>
Cc: Jason Molenda <jason-swarelist@molenda.com>,
	overseers@sources.redhat.com
Subject: Re: [Fwd: failure notice]
Date: Wed, 30 Aug 2000 14:01:00 -0000	[thread overview]
Message-ID: <20000830170040.A28076@cygnus.com> (raw)
Message-ID: <20000830140100.yCzXgQGmpDvAsX5Y1xWZ8udn7Zfmt_NSpQZzSVhHIY0@z> (raw)
In-Reply-To: <39AD73E6.5A848A10@redhat.com>

On Wed, Aug 30, 2000 at 09:51:50PM +0100, Jonathan Larmour wrote:
>Looking at check-for-listname.sh (thanks for the pointer Crash), the
>relevant line is:
>if cat $TMPFILE | sed -n '/^[Cc][Cc]: /,/^[a-zA-Z]/p' | sed '$d' |
>   egrep -i "$VALID_LISTNAME" >/dev/null 2>&1                     
>
>If the "sed '$d' |" is removed, it works correctly on this mail. I can't
>see any reason for the "sed '$d'" to be there. Is there one? If not, I'll
>just remove it.

I think that the $d guards against something like:

To: greatopportunities@foryou.com,
    dontmiss@this.com
Subject: ecos-discuss@sourceware.cygnus.com

Admittedly, it's not likely that something like this would happen, but this
should be moot anyway.  I've checked in a patch which should solve this problem.

I've checked it on the header in question and it seems to work fine.

Now, let's see if there are thousands of angry screams when we find that this
only works for ecos-discuss@sourceware.cygnus.com...

cgf

  parent reply	other threads:[~2000-12-30  6:08 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
2000-08-30 14:01             ` Chris Faylor
2000-12-30  6:08             ` Jonathan Larmour
2000-08-30 14:13               ` Jonathan Larmour
  -- 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 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
2000-07-07 18:46       ` Jim Kingdon
2000-12-30  6:08       ` Chris Faylor
2000-07-07 19:05         ` Chris 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=20000830170040.A28076@cygnus.com \
    --to=cgf@cygnus.com \
    --cc=jason-swarelist@molenda.com \
    --cc=jlarmour@redhat.com \
    --cc=overseers@sources.redhat.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).