From: Sebastian Schuberth <sschuberth@gmail.com>
To: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [ANNOUNCE] Git v2.8.0-rc0
Date: Mon, 29 Feb 2016 10:24:21 +0100 [thread overview]
Message-ID: <56D40E45.5020304@gmail.com> (raw)
In-Reply-To: <xmqqmvqnhwf4.fsf@gitster.mtv.corp.google.com>
On 2/27/2016 0:41, Junio C Hamano wrote:
> * Some calls to strcpy(3) triggers a false warning from static
> analysers that are less intelligent than humans, and reducing the
> number of these false hits helps us notice real issues. A few
> calls to strcpy(3) in test-path-utils that are already safe has
> been rewritten to avoid false wanings.
>
> * Some calls to strcpy(3) triggers a false warning from static
> analysers that are less intelligent than humans, and reducing the
> number of these false hits helps us notice real issues. A few
> calls to strcpy(3) in "git rerere" that are already safe has been
> rewritten to avoid false wanings.
This is a duplicate.
Regards,
Sebastian
prev parent reply other threads:[~2016-02-29 9:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-26 23:41 [ANNOUNCE] Git v2.8.0-rc0 Junio C Hamano
2016-02-27 11:10 ` Christian Couder
2016-02-27 17:46 ` Junio C Hamano
2016-02-29 9:24 ` Sebastian Schuberth [this message]
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=56D40E45.5020304@gmail.com \
--to=sschuberth@gmail.com \
--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.