From: "René Scharfe" <l.s.r@web.de>
To: Git List <git@vger.kernel.org>
Cc: Junio C Hamano <gitster@pobox.com>
Subject: [PATCH 0/3] COPY_ARRAY, MOVE_ARRAY, DUP_ARRAY
Date: Fri, 30 Dec 2022 22:51:23 +0100 [thread overview]
Message-ID: <efe7ec20-201e-a1c1-8e16-2f714a0aee8e@web.de> (raw)
Tighten the type check of COPY_ARRAY and MOVE_ARRAY. Then add DUP_ARRAY
for making a shallow copy without repeating destination and element
count, which inherits the stricter check.
do full type check in COPY_ARRAY and MOVE_ARRAY
add DUP_ARRAY
use DUP_ARRAY
attr.c | 3 +--
builtin/am.c | 3 +--
commit-graph.c | 3 +--
commit-reach.c | 3 +--
compat/mingw.c | 3 +--
contrib/coccinelle/array.cocci | 7 +++++++
git-compat-util.h | 7 +++++++
parse-options.c | 3 +--
pathspec.c | 6 ++----
9 files changed, 22 insertions(+), 16 deletions(-)
--
2.39.0
next reply other threads:[~2022-12-30 21:51 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-30 21:51 René Scharfe [this message]
2022-12-30 21:56 ` [PATCH 1/3] do full type check in COPY_ARRAY and MOVE_ARRAY René Scharfe
2023-01-01 3:03 ` Junio C Hamano
2023-01-01 3:59 ` Junio C Hamano
2023-01-01 7:41 ` René Scharfe
2023-01-01 10:45 ` René Scharfe
2023-01-01 12:11 ` Junio C Hamano
2023-01-01 12:32 ` René Scharfe
2023-01-01 12:46 ` Junio C Hamano
2022-12-30 22:02 ` [PATCH 2/3] add DUP_ARRAY René Scharfe
2022-12-30 22:03 ` [PATCH 3/3] use DUP_ARRAY René Scharfe
2023-01-01 21:05 ` [PATCH v2 0/4] COPY_ARRAY, MOVE_ARRAY, DUP_ARRAY René Scharfe
2023-01-01 21:08 ` [PATCH v2 1/4] factor out BARF_UNLESS_COPYABLE René Scharfe
2023-01-01 21:11 ` [PATCH v2 2/4] do full type check in BARF_UNLESS_COPYABLE René Scharfe
2023-01-08 7:28 ` Junio C Hamano
2023-01-08 10:10 ` René Scharfe
2023-01-09 4:27 ` Junio C Hamano
2023-01-09 18:08 ` Jeff Hostetler
2023-01-01 21:14 ` [PATCH v2 3/4] add DUP_ARRAY René Scharfe
2023-01-01 21:16 ` [PATCH v2 4/4] use DUP_ARRAY René Scharfe
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=efe7ec20-201e-a1c1-8e16-2f714a0aee8e@web.de \
--to=l.s.r@web.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).