All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Branchaud <marcnarc@xiplink.com>
To: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Cc: "Kyle J. McKay" <mackyle@gmail.com>, Eric Wong <normalperson@yhbt.net>
Subject: Re: [ANNOUNCE] Git v1.8.5-rc2
Date: Thu, 14 Nov 2013 11:47:04 -0500	[thread overview]
Message-ID: <5284FE88.8040208@xiplink.com> (raw)
In-Reply-To: <xmqqsiuzdhov.fsf@gitster.dls.corp.google.com>

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

  reply	other threads:[~2013-11-14 16:46 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 [this message]
2013-11-18 17:01   ` Junio C Hamano
2013-11-18 18:49     ` Junio C Hamano
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=5284FE88.8040208@xiplink.com \
    --to=marcnarc@xiplink.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=mackyle@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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.