From: Mike Dahmus <mdahmus@potomacfusion.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: RE: Repeated problems with svn even after rebaseall and peflagsall on Windows 7
Date: Thu, 19 May 2011 15:26:00 -0000 [thread overview]
Message-ID: <688D8B269DCBDE44A466DC43D403624C0155CCFE40@pfi-mail> (raw)
In-Reply-To: <20110517011110.GA22552@ednor.casa.cgf.cx>
Nope, didn't help; in fact, the rebase at 0x77000000 (whatever the recommendation 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 this way"? I've been as stalwart a defender of cygwin as you'd find at my various companies over the years but this wart is getting really hard to ignore. In particular, since I myself can't do subversion or various other things 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
next prev parent reply other threads:[~2011-05-19 15:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-17 0:27 Mike Dahmus
2011-05-17 1:11 ` Christopher Faylor
2011-05-19 15:26 ` Mike Dahmus [this message]
2011-05-19 15:32 ` Larry Hall (Cygwin)
2011-05-19 15:39 ` Christopher Faylor
2011-05-19 15:55 ` Larry Hall (Cygwin)
2011-05-19 19:12 ` Mike Dahmus
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=688D8B269DCBDE44A466DC43D403624C0155CCFE40@pfi-mail \
--to=mdahmus@potomacfusion.com \
--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).