From: Ben Walton <bwalton@artsci.utoronto.ca>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: normalperson <normalperson@yhbt.net>, git <git@vger.kernel.org>
Subject: Re: [PATCH] Escape file:// URL's to meet subversion SVN::Ra requirements
Date: Wed, 02 Nov 2011 15:05:00 -0400 [thread overview]
Message-ID: <1320260449-sup-479@pinkfloyd.chass.utoronto.ca> (raw)
In-Reply-To: <20111102182015.GA11401@elie.hsd1.il.comcast.net>
Excerpts from Jonathan Nieder's message of Wed Nov 02 14:20:38 -0400 2011:
> Thanks for your work on this! I'm not really sure how one can
> decide that the problem is not in svn --- some existing functions
> changed ABI in such a way as to break existing applications and
> require code changes and a recompile. It would be better for
> Subversion to silently fix up paths provided by bad callers, or at
> least to return a sensible error code.
Yes, my apologies. I wrote this commit message before fully realizing
just how wrong the response on the svn list was. It core dumps, after
all...If the patch is useful, I'll resubmit with a better commit
message.
> So the problem is that nobody who cared was testing prereleases of
> subversion and reporting bugs early enough for it to get this fixed
> before the 1.7 release. But yes, that's water under the bridge and
> git-svn (and libsvn-perl, and pysvn, and ...) should just adjust to
> the new world order.
>
> > [1] http://news.gmane.org/gmane.comp.version-control.subversion.devel
>
> Do you mean
> http://thread.gmane.org/gmane.comp.version-control.subversion.devel/132250
> ?
No, the link should have been:
http://article.gmane.org/gmane.comp.version-control.subversion.devel/132227
I'm not sure how it got mangled like that.
> | # failed 1 among 2 test(s)
> | 1..2
> | make[3]: *** [t9145-git-svn-master-branch.sh] Error 1
>
> Does it work for you? This is with a merge of git 1.7.8-rc0 and
> 1.7.7.2.
Yikes...I had svn tests turned off in my global build script still and
only validated this against t9134. My apologies. I'll submit
something proper later this evening. (Assuming I get a working patch
that passes the whole suite.)
Sorry for the clumsy patch.
Thanks
-Ben
--
Ben Walton
Systems Programmer - CHASS
University of Toronto
C:416.407.5610 | W:416.978.4302
next prev parent reply other threads:[~2011-11-02 19:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-02 16:38 (unknown), Ben Walton
2011-11-02 16:38 ` [PATCH] Escape file:// URL's to meet subversion SVN::Ra requirements Ben Walton
2011-11-02 18:20 ` Jonathan Nieder
2011-11-02 19:05 ` Ben Walton [this message]
2011-11-02 22:09 ` Eric Wong
2011-11-04 2:11 ` Ben Walton
2011-11-04 6:38 ` Jonathan Nieder
2012-07-16 20:16 ` Michael Witten
2011-12-17 8:45 ` Jonathan Nieder
2011-12-17 9:50 ` Jonathan Nieder
2011-12-17 23:48 ` Ben Walton
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1320260449-sup-479@pinkfloyd.chass.utoronto.ca \
--to=bwalton@artsci.utoronto.ca \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--cc=normalperson@yhbt.net \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).