public inbox for cygwin-talk@cygwin.com
 help / color / mirror / Atom feed
From: "Dave Korn" <dave.korn@artimi.com>
To: "'zap splat blong'" <cygwin-talk@cygwin.com>
Subject: RE: 1.5.19-4 & snapshot-20060529 : crash when freeing null std::string   in dll (resend for attachment renaming)
Date: Thu, 01 Jun 2006 09:29:00 -0000	[thread overview]
Message-ID: <045f01c6855d$cfd47d60$a501a8c0@CAM.ARTIMI.COM> (raw)
In-Reply-To: <e5krl5$qdq$1@sea.gmane.org>

On 31 May 2006 20:44, mwoehlke wrote:

> Dave Korn wrote:
>> On 31 May 2006 19:29, LenX wrote:
>>> (resend for attachment renaming)
>> 
>>   That was completely stupid and pointless.  You spammed the list with
>> 500k of duplicate rubbish just because you wanted to change the names?  
>> That's really SOOOOooo worth it for everyone else.  NOT!  FCOL, why didn't
>> you just send a short email listing the new names?
> 
> In all fairness, he probably did that because he received a bounce
> notification, just like I did when I posted a .bz2... not from the list,
> but from the over-zealous AV filter of someone *subscribed to* the list
> (say, I thought such bounces were supposed to go to the list admin, not
> the list poster?).

  Yeh, but OTOH the whole thing was 99% binaries, which anyone interested
could build themselves from the source, so it was a real department of
redundancy department situation!
 
> ...Meaning he failed to pay attention to where the e-mail came from and
> did, as you noted, spam the list with another half MB of attachment. The
> correct response would have been to a: ignore it (what I did), or b:
> send a follow-up suggesting that anyone that didn't get the attachment
> find it via the archives.

  That doesn't help all the people on dialup who already got it twice, though.

  At least I didn't reply to his post and inadvertently quote the entire
tarball in uucode/b64 though.  I've seen that happen!

    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....

  reply	other threads:[~2006-06-01  9:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <447DE070.6070609@gmail.com>
     [not found] ` <03e901c684e0$fbf906e0$a501a8c0@CAM.ARTIMI.COM>
2006-05-31 19:44   ` mwoehlke
2006-06-01  9:29     ` Dave Korn [this message]
2006-06-07 16:20 Williams, Gerald S (Jerry)
2006-06-07 16:25 ` Dave Korn

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='045f01c6855d$cfd47d60$a501a8c0@CAM.ARTIMI.COM' \
    --to=dave.korn@artimi.com \
    --cc=cygwin-talk@cygwin.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).