From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jul 2018, #03; Wed, 25)
Date: Thu, 26 Jul 2018 09:57:42 -0700 [thread overview]
Message-ID: <xmqqlg9yq6ih.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <20180726072429.GA7625@sigill.intra.peff.net> (Jeff King's message of "Thu, 26 Jul 2018 03:24:29 -0400")
Jeff King <peff@peff.net> writes:
> On Wed, Jul 25, 2018 at 03:13:37PM -0700, Junio C Hamano wrote:
>
>> * jk/banned-function (2018-07-24) 5 commits
>> - banned.h: mark strncpy() as banned
>> - banned.h: mark sprintf() as banned
>> - banned.h: mark strcat() as banned
>> - automatically ban strcpy()
>> - Merge branch 'sb/blame-color' into jk/banned-function
>>
>> It is too easy to misuse system API functions such as strcat();
>> these selected functions are now forbidden in this codebase and
>> will cause a compilation failure.
>>
>> Will merge to 'next'.
>
> Eric nudged me over the fence to use a slightly different mechanism to
> generate the error. See:
>
> https://public-inbox.org/git/20180726072105.GA6057@sigill.intra.peff.net/
>
> It looks like sb/blame-color graduated, so this could also just be
> applied directly on master now to avoid the funky merge.
OK. Is it that "you cannot call a variable" thing?
next prev parent reply other threads:[~2018-07-26 16:57 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-25 22:13 What's cooking in git.git (Jul 2018, #03; Wed, 25) Junio C Hamano
2018-07-25 22:56 ` Stefan Beller
2018-07-25 23:43 ` Junio C Hamano
2018-07-26 4:14 ` Junio C Hamano
2018-07-26 16:56 ` Junio C Hamano
2018-07-25 23:47 ` Junio C Hamano
2018-07-25 23:48 ` Junio C Hamano
2018-07-26 4:15 ` Junio C Hamano
2018-07-26 6:07 ` Оля Тележная
2018-07-26 16:57 ` Junio C Hamano
2018-08-02 12:41 ` Christian Couder
2018-08-02 18:40 ` Junio C Hamano
2018-07-26 7:24 ` Jeff King
2018-07-26 16:57 ` Junio C Hamano [this message]
2018-07-26 20:46 ` Jeff King
2018-07-27 14:28 ` Ævar Arnfjörð Bjarmason
2018-07-27 17:28 ` Junio C Hamano
2018-07-30 13:16 ` range-diff, was " Johannes Schindelin
2018-07-30 15:41 ` Junio C Hamano
2018-08-01 16:01 ` Johannes Schindelin
2018-08-01 19:11 ` Junio C Hamano
2018-08-01 20:44 ` ds/reachable (was Re: What's cooking in git.git (Jul 2018, #03; Wed, 25)) Derrick Stolee
2018-08-01 21:55 ` Junio C Hamano
2018-08-01 20:53 ` ds/multi-pack-index " Derrick Stolee
2018-08-01 22:13 ` Junio C Hamano
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqlg9yq6ih.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).