All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Torsten Bögershausen" <tboegi@web.de>
To: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [ANNOUNCE] Git v2.7.4 (and updates to older maintenance tracks)
Date: Fri, 18 Mar 2016 09:29:38 +0100	[thread overview]
Message-ID: <56EBBC72.7000201@web.de> (raw)
In-Reply-To: <xmqqlh5gzuc8.fsf@gitster.mtv.corp.google.com>

> Git v2.7.4 Release Notes
> ========================
> 
> Fixes since v2.7.3
> ------------------
> 
>  * Bugfix patches were backported from the 'master' front to plug heap
>    corruption holes, to catch integer overflow in the computation of
>    pathname lengths, and to get rid of the name_path API.  Both of
>    these would have resulted in writing over an under-allocated buffer
>    when formulating pathnames while tree traversal.
> 
> ----------------------------------------------------------------
> 
> Changes since v2.7.3 are as follows:
> 
> Jeff King (7):
>       add helpers for detecting size_t overflow
>       tree-diff: catch integer overflow in combine_diff_path allocation
>       http-push: stop using name_path
>       show_object_with_name: simplify by using path_name()
>       list-objects: convert name_path to a strbuf
>       list-objects: drop name_path entirely
>       list-objects: pass full pathname to callbacks
> 
If there is a new 2.7.x release, does it make sense to cherry-pick this one:

commit 7b6daf8d2fee1a9866b1d4eddbfaa5dbc42c5dbb
Author: Torsten Bögershausen <tboegi@web.de>
Date:   Sun Feb 28 21:09:44 2016 +0100

    config.mak.uname: use clang for Mac OS X 10.6
    

  reply	other threads:[~2016-03-18  8:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-17 21:07 [ANNOUNCE] Git v2.7.4 (and updates to older maintenance tracks) Junio C Hamano
2016-03-18  8:29 ` Torsten Bögershausen [this message]
2016-03-20 15:32 ` Renato Botelho
2016-03-20 17:07   ` Eric Sunshine
2016-03-20 19:43     ` Jeff King
2016-03-21  4:41       ` Eric Sunshine
2016-03-21 13:33         ` Renato Botelho

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=56EBBC72.7000201@web.de \
    --to=tboegi@web.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    /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.