X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=2.9 required=5.0 tests=AWL,BAYES_40,TW_SV,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org From: Mike Dahmus To: "cygwin AT cygwin DOT com" Date: Thu, 19 May 2011 10:25:48 -0500 Subject: RE: Repeated problems with svn even after rebaseall and peflagsall on Windows 7 Message-ID: <688D8B269DCBDE44A466DC43D403624C0155CCFE40@pfi-mail> References: <20110517011110 DOT GA22552 AT ednor DOT casa DOT cgf DOT cx> In-Reply-To: <20110517011110.GA22552@ednor.casa.cgf.cx> Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Nope, didn't help; in fact, the rebase at 0x77000000 (whatever the recommen= dation was) broke things much worse; and now even bash won't start without = a million access violations. Why is this even necessary anyways? Other than "because it's always been th= is way"? I've been as stalwart a defender of cygwin as you'd find at my var= ious companies over the years but this wart is getting really hard to ignor= e. In particular, since I myself can't do subversion or various other thing= s any more without devolving to something like (ugh) tortoise. -- 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