From: Robert Collins <rbcollins@cygwin.com>
To: Brian Dessent <brian@dessent.net>
Cc: cygwin@cygwin.com
Subject: Re: Setup snapshot location?
Date: Tue, 04 Nov 2003 04:27:00 -0000 [thread overview]
Message-ID: <1067920051.2316.47.camel@localhost> (raw)
In-Reply-To: <3FA7298B.657FC399@dessent.net>
[-- Attachment #1: Type: text/plain, Size: 414 bytes --]
On Tue, 2003-11-04 at 15:22, Brian Dessent wrote:
> http://www.cygwin.com/setup-snapshots/
>
> I agree that this fact has not exactly been well publicised, I don't
> know if there's a reason for that or not.
Yes, because I want to advise folk when a snapshot should be tested. The
setup home page is more publicised.
Rob
--
GPG key available at: <http://members.aardvark.net.au/lifeless/keys.txt>.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2003-11-04 4:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-04 4:15 Vince Rice
2003-11-04 4:20 ` Robert Collins
2003-11-04 4:22 ` Brian Dessent
2003-11-04 4:27 ` Robert Collins [this message]
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=1067920051.2316.47.camel@localhost \
--to=rbcollins@cygwin.com \
--cc=brian@dessent.net \
--cc=cygwin@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).