From: David Boyce <dsb@boyski.com>
To: cygwin@cygwin.com
Subject: Re: regression in subversion with 1.7.18 (and .19)
Date: Thu, 30 May 2013 02:18:00 -0000 [thread overview]
Message-ID: <CACUHbYOzymJ4tT2226z+RgLBaHdV6=iW6jU45AonDzWhAcziYw@mail.gmail.com> (raw)
In-Reply-To: <51A66732.3080103@acm.org>
On Wed, May 29, 2013 at 1:38 PM, David Rothenberger <daveroth@acm.org> wrote:
> I think the recently release subversion-1.7.9-2 package will fix your
> problem. It does not fix all uses of UNC paths, especially those passed
> on the command line (e.g., "svn status //server/share" or "svn export
> //server/share") because those require teaching libapr1 about UNC paths,
> which I haven't done (yet?).
>
> Still, I think it will support your use case of the config directory on
> a UNC share.
>
> Please give it a shot and let me know.
My local test case now works perfectly. Thanks!
-David Boyce
--
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
prev parent reply other threads:[~2013-05-30 1:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-27 22:38 David Boyce
2013-05-28 4:47 ` David Rothenberger
2013-05-29 21:23 ` David Rothenberger
2013-05-30 2:18 ` David Boyce [this message]
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='CACUHbYOzymJ4tT2226z+RgLBaHdV6=iW6jU45AonDzWhAcziYw@mail.gmail.com' \
--to=dsb@boyski.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).