Re: [ANNOUNCE] Git v1.8.5-rc2
On 13-11-18 01:49 PM, Junio C Hamano wrote: > Junio C Hamano writes: > >> Marc Branchaud writes: >> Foreign interfaces, subsystems and ports. * "git-svn" used with SVN 1.8.0 when talking over https:// connection dumped core due to a bug in the serf library that SVN uses. Work it around on our side, even though the SVN side is being fixed. ... * Subversion 1.8.0 that was recently released breaks older subversion clients coming over http/https in various ways. >>> >>> Isn't this the same as the serf fixes ([1],[2])? If not, what git change is >>> it referring to? >> >> The latter, I think, is 8ac251b6 (git-svn: allow git-svn fetching to >> work using serf, 2013-07-06). Without it we won't even work with >> newer SVN library. >> >> The former I think refers to 73ffac3b (git-svn: fix termination >> issues for remote svn connections, 2013-09-03). Even with the serf >> support, without a work-around, we won't work with serf. >> >> The description can and should be rolled into one, but I am not sure >> what the best wording would be. >> >> Thanks. > > I'd keep them as separate entries, like so: > > * "git-svn" has been taught to use the serf library, which is the >only option SVN 1.8.0 offers us when talking the HTTP protocol. > > * "git-svn" talking over https:// connection using the serf library s/talking over https/talking over an https/ >dumped core due to a bug in the serf library that SVN uses. Work >around it on our side, even though the SVN side is being fixed. Those look good to my layman's eyes. M. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [ANNOUNCE] Git v1.8.5-rc2
Junio C Hamano writes: > Marc Branchaud writes: > >>> Foreign interfaces, subsystems and ports. >>> >>> * "git-svn" used with SVN 1.8.0 when talking over https:// connection >>>dumped core due to a bug in the serf library that SVN uses. Work >>>it around on our side, even though the SVN side is being fixed. >>> ... >>> * Subversion 1.8.0 that was recently released breaks older subversion >>>clients coming over http/https in various ways. >> >> Isn't this the same as the serf fixes ([1],[2])? If not, what git change is >> it referring to? > > The latter, I think, is 8ac251b6 (git-svn: allow git-svn fetching to > work using serf, 2013-07-06). Without it we won't even work with > newer SVN library. > > The former I think refers to 73ffac3b (git-svn: fix termination > issues for remote svn connections, 2013-09-03). Even with the serf > support, without a work-around, we won't work with serf. > > The description can and should be rolled into one, but I am not sure > what the best wording would be. > > Thanks. I'd keep them as separate entries, like so: * "git-svn" has been taught to use the serf library, which is the only option SVN 1.8.0 offers us when talking the HTTP protocol. * "git-svn" talking over https:// connection using the serf library dumped core due to a bug in the serf library that SVN uses. Work around it on our side, even though the SVN side is being fixed. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [ANNOUNCE] Git v1.8.5-rc2
Marc Branchaud writes: >> Foreign interfaces, subsystems and ports. >> >> * "git-svn" used with SVN 1.8.0 when talking over https:// connection >>dumped core due to a bug in the serf library that SVN uses. Work >>it around on our side, even though the SVN side is being fixed. >> ... >> * Subversion 1.8.0 that was recently released breaks older subversion >>clients coming over http/https in various ways. > > Isn't this the same as the serf fixes ([1],[2])? If not, what git change is > it referring to? The latter, I think, is 8ac251b6 (git-svn: allow git-svn fetching to work using serf, 2013-07-06). Without it we won't even work with newer SVN library. The former I think refers to 73ffac3b (git-svn: fix termination issues for remote svn connections, 2013-09-03). Even with the serf support, without a work-around, we won't work with serf. The description can and should be rolled into one, but I am not sure what the best wording would be. Thanks. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [ANNOUNCE] Git v1.8.5-rc2
On 13-11-13 06:07 PM, Junio C Hamano wrote: > A release candidate Git v1.8.5-rc2 is now available for testing > at the usual places. [ snip ] > Updates since v1.8.4 > > > Foreign interfaces, subsystems and ports. > > * "git-svn" used with SVN 1.8.0 when talking over https:// connection >dumped core due to a bug in the serf library that SVN uses. Work >it around on our side, even though the SVN side is being fixed. > > * On MacOS X, we detected if the filesystem needs the "pre-composed >unicode strings" workaround, but did not automatically enable it. >Now we do. > > * remote-hg remote helper misbehaved when interacting with a local Hg >repository relative to the home directory, e.g. "clone hg::~/there". > > * imap-send ported to OS X uses Apple's security framework instead of >OpenSSL one. > > * Subversion 1.8.0 that was recently released breaks older subversion >clients coming over http/https in various ways. Isn't this the same as the serf fixes ([1],[2])? If not, what git change is it referring to? BTW, $ git log --no-merges --oneline v1.8.4..v1.8.5-rc2 -- git-svn.perl perl/Git/SVN/ shows: f849bb6 git-svn: Warn about changing default for --prefix in Git v2.0 60786bd git-svn: fix signed commit parsing 73ffac3 git-svn: fix termination issues for remote svn connections 8ac251b git-svn: allow git-svn fetching to work using serf The release notes don't seem to mention 60786bd. M. [1] http://thread.gmane.org/gmane.comp.version-control.git/229720 [2] http://thread.gmane.org/gmane.comp.version-control.git/233701 -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
