X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-1.1 required=5.0 	tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SARE_MSGID_LONG45,T_TO_NO_BRKTS_FREEMAIL
X-Spam-Check-By: sourceware.org
MIME-Version: 1.0
In-Reply-To: <op.vat3u0zb1e62zd@merlin.emma.line.org>
References: <4BB29285 DOT 4010701 AT gmail DOT com> 	 <20100331042545 DOT GA23824 AT ednor DOT casa DOT cgf DOT cx> 	 <4BB3F897 DOT 7090306 AT gmail DOT com> <4BBD42BC DOT 4050404 AT gmail DOT com> 	 <20100408061139 DOT GA27780 AT ednor DOT casa DOT cgf DOT cx> 	 <op DOT vat3u0zb1e62zd AT merlin DOT emma DOT line DOT org>
Date: Thu, 8 Apr 2010 08:17:25 -0400
Received: by 10.229.212.213 with SMTP id gt21mr111970qcb.2.1270729045625; Thu,  	08 Apr 2010 05:17:25 -0700 (PDT)
Message-ID: <j2i30e4a071004080517ga544d4fu69405346be665474@mail.gmail.com>
Subject: Re: git on cygwin 1.7.2/1.7.4
From: Mark Levedahl <mlevedahl AT gmail DOT com>
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset=ISO-8859-1
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

On Thu, Apr 8, 2010 at 4:14 AM, Matthias Andree <matthias DOT andree AT gmx DOT de> wrote:
> Am 08.04.2010, 08:11 Uhr, schrieb Christopher Faylor:

>
> Not to suggest anything particular to Mark, but rather as a general comment:
> I wonder how many of the "1.7.X no better" can be attributed to the
> replace-on-reboot failure up to and including setup 2.693. If people rely on
> that rather than running "uname -a" or similar, those that were told to
> reboot may be unaware they're using the older version.
>
> --

When doing my testing, I explictly stopped all cygwin processes,
copied whichever cygwin1.dll (1.7.2, .3, .4, snapshot) I wished to
test into /bin (and Windows is very good about complaining when a
cygwin process is still running when trying to overwrite the dll),
fired up a shell, ran "uname -a" to assure I had what I thought I had.
 So, I am quite sure of what I was running.

Mark

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple