From: Junio C Hamano <gitster@pobox•com>
To: Marc Branchaud <marcnarc@xiplink•com>
Cc: git@vger•kernel.org, "Kyle J. McKay" <mackyle@gmail•com>,
Eric Wong <normalperson@yhbt•net>
Subject: Re: [ANNOUNCE] Git v1.8.5-rc2
Date: Mon, 18 Nov 2013 10:49:40 -0800 [thread overview]
Message-ID: <xmqqiovpbl4r.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <xmqqvbzpbq4d.fsf@gitster.dls.corp.google.com> (Junio C. Hamano's message of "Mon, 18 Nov 2013 09:01:54 -0800")
Junio C Hamano <gitster@pobox•com> writes:
> Marc Branchaud <marcnarc@xiplink•com> 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.
next prev parent reply other threads:[~2013-11-18 18:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-13 23:07 [ANNOUNCE] Git v1.8.5-rc2 Junio C Hamano
2013-11-14 16:47 ` Marc Branchaud
2013-11-18 17:01 ` Junio C Hamano
2013-11-18 18:49 ` Junio C Hamano [this message]
2013-11-18 19:42 ` Marc Branchaud
2013-11-14 17:01 ` [PATCH] RelNotes: Spelling & grammar fixes Marc Branchaud
2013-11-15 15:26 ` Marc Branchaud
2013-11-18 18:42 ` Junio C Hamano
2013-11-18 19:52 ` Marc Branchaud
2013-11-18 20:00 ` Jonathan Nieder
2013-11-18 22:12 ` Junio C Hamano
2013-11-18 19:58 ` Jonathan Nieder
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=xmqqiovpbl4r.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=mackyle@gmail$(echo .)com \
--cc=marcnarc@xiplink$(echo .)com \
--cc=normalperson@yhbt$(echo .)net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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