public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Larry Hall (RFK Partners, Inc)" <lhall@rfk.com>
To: "Alexei Lioubimov" <e-complex@mtu-net.ru>, <cygwin@cygwin.com>
Subject: Re: setup 2.194.2.24: Bug (?) in downloading from internet
Date: Thu, 25 Apr 2002 11:00:00 -0000	[thread overview]
Message-ID: <4.3.1.2.20020425112359.02c46c58@pop.ma.ultranet.com> (raw)
In-Reply-To: <000b01c1ec6b$18941be0$8341fea9@ael>

At 11:08 AM 4/25/2002, Alexei Lioubimov wrote:
>Hello,
>I have a problem using setup.exe. Here is the description
>
>setup.exe: 2.194.2.24;
>mode: Download from Inernet;
>keyword: "skip" flag;
>
>The problem: if i've downloaded some tarballs and didn't install them - then
>during the following updates the SETUP program doesn't report me about that.
>It simply marks those files as "skip" by default and allows me to change
>this to the current version. But i may have already downloaded the stuff...
>So i caught myself downloading the same tarballs twice or triple times. If
>you take into account the slow speed of dial-up connection, that i have,
>then you can imagine what i'm feeling.
>
>The suggestion: may be it's possible force SETUP consider "current" be
>"downloaded" but not "installed" stuff during "Download from Internet"
>process?



This has already been reported.  If you're interested in the discussion on
this subject, please see the email list archives.



Larry Hall                              lhall@rfk.com
RFK Partners, Inc.                      http://www.rfk.com
838 Washington Street                   (508) 893-9779 - RFK Office
Holliston, MA 01746                     (508) 893-9889 - FAX


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

  reply	other threads:[~2002-04-25 15:26 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-25  8:55 Alexei Lioubimov
2002-04-25 11:00 ` Larry Hall (RFK Partners, Inc) [this message]
2002-04-26  7:03   ` Alexei Lioubimov
2002-04-26  7:10 Robert Collins
2002-04-26  7:57 ` Alexei Lioubimov
2002-04-26  8:34 Robert Collins
2002-04-28  3:17 Daniele Mezzetti
2002-04-28  4:31 ` Sam Edge
2002-04-28  4:47 Robert Collins
2002-04-28  8:08 ` Sam Edge
2002-04-28 15:04 ` Gary R. Van Sickle
2002-04-28 15:09   ` Sam Edge
2002-04-28 15:30     ` Charles Wilson
2002-04-28 16:05       ` Christopher Faylor
2002-04-28 16:09         ` Sam Edge
2002-04-28 19:08         ` Michael A Chase
2002-04-29  0:06           ` Christopher Faylor
2002-04-29  0:57             ` Cliff Hones
2002-04-29  4:58               ` Robert Collins
2002-04-28 16:05       ` Sam Edge
2002-04-29  4:07 ` Max Bowsher
2002-04-29  4:24   ` Robert Collins
2002-04-28  8:14 Robert Collins
2002-04-28  9:56 ` Kurt Roeckx
2002-04-28 10:15 Robert Collins
2002-04-28 22:34 Alec Mihailovs
2002-04-28 23:51 ` Charles Wilson
2002-04-29  2:26 Robert Collins
2002-04-29  5:42 ` Sam Edge
2002-04-29  5:49   ` Robert Collins
2002-04-29  7:46     ` Sam Edge
2002-04-30  1:58       ` Gary R. Van Sickle
2002-04-29  8:27     ` Christopher Faylor
2002-04-29  2:35 Robert Collins

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=4.3.1.2.20020425112359.02c46c58@pop.ma.ultranet.com \
    --to=lhall@rfk.com \
    --cc=cygwin@cygwin.com \
    --cc=e-complex@mtu-net.ru \
    /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).