| delorie.com/archives/browse.cgi | search |
| X-Recipient: | archive-cygwin AT delorie DOT com |
| X-SWARE-Spam-Status: | No, hits=-1.8 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE |
| X-Spam-Check-By: | sourceware.org |
| X-Mail-Handler: | MailHop Outbound by DynDNS |
| X-Report-Abuse-To: | abuse AT dyndns DOT com (see http://www.dyndns.com/services/mailhop/outbound_abuse.html for abuse reporting information) |
| X-MHO-User: | U2FsdGVkX19BHbnQ2go0hzxPrvO6mqxR |
| Date: | Mon, 30 Jan 2012 11:16:49 -0500 |
| From: | Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com> |
| To: | cygwin AT cygwin DOT com |
| Subject: | Re: "git clone" over ssh fails intermittently w/snapshot 20120123 |
| Message-ID: | <20120130161649.GA8413@ednor.casa.cgf.cx> |
| Reply-To: | cygwin AT cygwin DOT com |
| Mail-Followup-To: | cygwin AT cygwin DOT com |
| References: | <26758 DOT 1327703355 AT freon DOT franz DOT com> <26967 DOT 1327703574 AT freon DOT franz DOT com> <20120128183816 DOT GA24438 AT ednor DOT casa DOT cgf DOT cx> <4332 DOT 1327939546 AT freon DOT franz DOT com> |
| MIME-Version: | 1.0 |
| In-Reply-To: | <4332.1327939546@freon.franz.com> |
| User-Agent: | Mutt/1.5.20 (2009-06-14) |
| Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
| 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 Mon, Jan 30, 2012 at 08:05:46AM -0800, Kevin Layer wrote: >Christopher Faylor wrote: >>> Is this new behavior just seen with this snapshot or is it something you >>> noticed in 1.7.9? If you've just seen it in the latest snapshot it >>> would be useful (as I've previously pleaded) to know in which snapshot >>> the bad behavior first showed up. > >Never seen until the snapshot was installed. That isn't precise enough. Are you saying that you saw the problem in the 2012-01-23 snapshot but not in the 2012-01-22 snapshot? I'll bet that you aren't. If you think this is a problem only manifested in snapshots then we need to know which snapshot first had the problem. >More info: > >Before the failure, I had removed and reinstalled cygwin, then >installed the snapshot. The machine on which git works was upgraded >little at a time. OTOH, "little at a time" might mean that you stepped through snapshots. However, since the only change to 2012-01-23 was to tweak fifos and, as far as I know, git clone doesn't use a fifo, it's hard to see why there would be a regression in 2012-01-23. cgf -- 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
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |