This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: cygwin processes and system'ed processes using 100% CPU

> -----Original Message-----
> From: cygwin-owner On Behalf Of Steven Hartland
> Sent: 27 January 2004 16:49
> To:
> Subject: Re: cygwin processes and system'ed processes using 100% CPU
> Sorry did I miss something where was the new issue?
>     Steve

  Here's (some of) the headers from your first post with the current subject

Message-ID: <01c601c3e4e3$f186d380$>
From: "Steven Hartland" <[REDACTED EMAIL ADDRESS]>
References: <>
Subject: cygwin processes and system'ed processes using 100% CPU
Date: Tue, 27 Jan 2004 14:43:35 -0000
MIME-Version: 1.0
Content-Type: multipart/mixed;

  The 'references' header shows that rather than starting a new mail and
entering the address of the ML in the To: field, you took the shortcut of
opening a mail you'd just received, hitting Reply, and replacing the subject
and contents with a new one.  The mail you replied to is this one from the
scp thread:

  Although some mailers, notably M$ ones, display the threading of posts
based purely on the Subject: header, others respect the References: header
and therefore place your post in the same thread as the one you were
replying to, even though you changed the subject.

  Using reply rather than starting a fresh mail is a natural enough way to
save yourself a bit of typing, but there's a bit of hidden persistent state
in there that not everyone knows about!

Can't think of a witty .sigline today....

Unsubscribe info:
Problem reports:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]