From: "Elijah Newren via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: Elijah Newren <newren@gmail.com>
Subject: [PATCH 0/2] Directory traversal fixes
Date: Thu, 27 May 2021 04:53:54 +0000 [thread overview]
Message-ID: <pull.961.git.1622091237.gitgitgadget@gmail.com> (raw)
This is a resend of the final two patches of my series, as per
https://lore.kernel.org/git/xmqqfsyht49j.fsf@gitster.g/. It will not merge
cleanly unless the last two patches of en/dir-traversal-fixes are first
reverted, as Junio suggested he'd be doing.
(Corrected Reviewed-by -> Signed-off-by in the first patch, minor stylistic
fix for the second.)
Derrick Stolee (1):
dir: update stale description of treat_directory()
Elijah Newren (1):
dir: introduce readdir_skip_dot_and_dotdot() helper
builtin/clean.c | 4 +---
builtin/worktree.c | 4 +---
diff-no-index.c | 5 ++---
dir.c | 38 ++++++++++++++++++++++----------------
dir.h | 2 ++
entry.c | 5 +----
notes-merge.c | 5 +----
object-file.c | 4 +---
packfile.c | 5 +----
rerere.c | 4 +---
worktree.c | 12 +++---------
11 files changed, 36 insertions(+), 52 deletions(-)
base-commit: dd55fc0df15c338a8dbec6dec6ca6b58edc8acef
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-961%2Fnewren%2Fdirectory-traversal-fixes-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-961/newren/directory-traversal-fixes-v1
Pull-Request: https://github.com/gitgitgadget/git/pull/961
--
gitgitgadget
next reply other threads:[~2021-05-27 4:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-27 4:53 Elijah Newren via GitGitGadget [this message]
2021-05-27 4:53 ` [PATCH 1/2] dir: update stale description of treat_directory() Derrick Stolee via GitGitGadget
2021-05-27 4:53 ` [PATCH 2/2] dir: introduce readdir_skip_dot_and_dotdot() helper Elijah Newren via GitGitGadget
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=pull.961.git.1622091237.gitgitgadget@gmail.com \
--to=gitgitgadget@gmail.com \
--cc=git@vger.kernel.org \
--cc=newren@gmail.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).