From: Daniel Ferreira <bnmvco@gmail.com>
To: git@vger.kernel.org
Cc: gitster@pobox.com, sbeller@google.com, pclouds@gmail.com,
mhagger@alum.mit.edu, Daniel Ferreira <bnmvco@gmail.com>
Subject: [PATCH v4 0/5] [GSoC] remove_subtree(): reimplement using iterators
Date: Tue, 28 Mar 2017 21:32:08 -0300 [thread overview]
Message-ID: <1490747533-89143-1-git-send-email-bnmvco@gmail.com> (raw)
Hi there,
This is the fourth version of the GSoC microproject of refactoring
remove_subtree() from recursively using readdir() to use dir_iterator. Below
are the threads for other versions:
v1: https://public-inbox.org/git/CAGZ79kZwT-9mHTiOJ5CEjk2wDFkn6+NcogjX0=vjhsAh16ANYg@mail.gmail.com/T/#t
v2: https://public-inbox.org/git/CACsJy8Dxh-QPBBLfaFWPAWUsbA9GVXA7x+mXLjEvYKhk1zOpig@mail.gmail.com/T/#t
v3: https://public-inbox.org/git/CAGZ79kYtpmURSQWPumobA=e3JBFjKhWCdv_LPhKCd71ZRwMovA@mail.gmail.com/T/#t
In this version of the patch, I followed Michael's suggestion
of splitting the commits responsible for adding the new feature to
dir_iterator. His suggestion of using flags instead of an options
struct has also been adopted.
This version also contains a test that is finally able to test the
function decently (not the one Stefan had suggested, which
did not result in a call to remove_subtree). I am just unsure about
its location in t/. I'd appreciate suggestions to put it in a more
decent home.
Daniel Ferreira (5):
dir_iterator: add helpers to dir_iterator_advance
dir_iterator: iterate over dir after its contents
remove_subtree(): reimplement using iterators
remove_subtree(): test removing nested directories
files_reflog_iterator: amend use of dir_iterator
dir-iterator.c | 105 +++++++++++++++++++++++++++++++---------
dir-iterator.h | 14 ++++--
entry.c | 31 ++++--------
refs/files-backend.c | 2 +-
t/t2000-checkout-cache-clash.sh | 11 +++++
5 files changed, 114 insertions(+), 49 deletions(-)
--
2.7.4 (Apple Git-66)
next reply other threads:[~2017-03-29 0:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-29 0:32 Daniel Ferreira [this message]
2017-03-29 0:32 ` [PATCH v4 1/5] dir_iterator: add helpers to dir_iterator_advance Daniel Ferreira
2017-03-29 4:32 ` Michael Haggerty
2017-03-29 0:32 ` [PATCH v4 2/5] dir_iterator: iterate over dir after its contents Daniel Ferreira
2017-03-29 9:56 ` Michael Haggerty
2017-03-29 10:44 ` Michael Haggerty
2017-03-29 16:46 ` Junio C Hamano
2017-03-30 4:59 ` Michael Haggerty
2017-03-30 6:08 ` Junio C Hamano
2017-03-30 6:39 ` Michael Haggerty
2017-03-30 11:08 ` Duy Nguyen
2017-04-02 4:25 ` Daniel Ferreira (theiostream)
2017-04-05 9:21 ` Duy Nguyen
2017-03-30 17:26 ` Junio C Hamano
2017-03-29 0:32 ` [PATCH v4 3/5] remove_subtree(): reimplement using iterators Daniel Ferreira
2017-03-29 10:01 ` Michael Haggerty
2017-03-29 0:32 ` [PATCH v4 4/5] remove_subtree(): test removing nested directories Daniel Ferreira
2017-03-29 0:32 ` [PATCH v4 5/5] files_reflog_iterator: amend use of dir_iterator Daniel Ferreira
2017-03-29 10:45 ` Michael Haggerty
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=1490747533-89143-1-git-send-email-bnmvco@gmail.com \
--to=bnmvco@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=mhagger@alum.mit.edu \
--cc=pclouds@gmail.com \
--cc=sbeller@google.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 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 NNTP newsgroup(s).