From: "Elijah Newren via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: bmalehorn@gmail.com, Elijah Newren <newren@gmail.com>
Subject: [PATCH 0/4] Clean cleanups
Date: Thu, 11 Jun 2020 06:59:29 +0000 [thread overview]
Message-ID: <pull.806.git.git.1591858774.gitgitgadget@gmail.com> (raw)
This fixes the performance regression reported at [1], and also performs a
few other cleanups found while investigating the issue.
[1]
https://lore.kernel.org/git/CAJB88a23uU2WfB0mnB9NfNbtgmABhNOWNOEMBt7rRVu7uL_C9A@mail.gmail.com/
Elijah Newren (4):
dir: fix a few confusing comments
dir, clean: avoid disallowed behavior
clean: consolidate handling of ignored parameters
clean: optimize and document cases where we recurse into
subdirectories
builtin/clean.c | 49 ++++++++++++++++++++++++++++++++++++++-----------
dir.c | 15 ++++++++++-----
2 files changed, 48 insertions(+), 16 deletions(-)
base-commit: 20514004ddf1a3528de8933bc32f284e175e1012
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-806%2Fnewren%2Fclean-cleanups-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-806/newren/clean-cleanups-v1
Pull-Request: https://github.com/git/git/pull/806
--
gitgitgadget
next reply other threads:[~2020-06-11 6:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-11 6:59 Elijah Newren via GitGitGadget [this message]
2020-06-11 6:59 ` [PATCH 1/4] dir: fix a few confusing comments Elijah Newren via GitGitGadget
2020-06-11 6:59 ` [PATCH 2/4] dir, clean: avoid disallowed behavior Elijah Newren via GitGitGadget
2020-06-11 6:59 ` [PATCH 3/4] clean: consolidate handling of ignored parameters Elijah Newren via GitGitGadget
2020-06-11 6:59 ` [PATCH 4/4] clean: optimize and document cases where we recurse into subdirectories Elijah Newren via GitGitGadget
2020-06-13 0:28 ` Junio C Hamano
2020-06-18 6:19 ` Brian Malehorn
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=pull.806.git.git.1591858774.gitgitgadget@gmail.com \
--to=gitgitgadget@gmail.com \
--cc=bmalehorn@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.
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.