public inbox for
 help / color / mirror / Atom feed
From: Christopher Faylor <>
Subject: Re: include SHA1/MD5 hash/digest of setup.exe, and HTTPS
Date: Fri, 28 Sep 2012 14:09:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <BLU166-W54FE3BE4C22757C5813DC0BE820@phx.gbl>

On Fri, Sep 28, 2012 at 09:26:16AM -0400, Mike Marchywka wrote:
>can you guys

No thanks.

And, yes, top-posting is still bad for all of the same reasons.

And, *forwarding* email rather than replying to it just exposes you
as rather clueless wrt email.

  reply	other threads:[~2012-09-28 14:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-28 12:56 Buchbinder, Barry (NIH/NIAID) [E]
2012-09-28 13:26 ` Mike Marchywka
2012-09-28 14:09   ` Christopher Faylor [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-09-28 14:20 Buchbinder, Barry (NIH/NIAID) [E]
2012-09-28  3:10 Mark Geisert

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).