From: "Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>
To: git@vger.kernel.org
Cc: "Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>
Subject: [PATCH 0/5] Globbing support in diff family
Date: Mon, 20 Sep 2010 09:29:55 +1000 [thread overview]
Message-ID: <1284939000-16907-1-git-send-email-pclouds@gmail.com> (raw)
This is on top of the pathspec struct series
http://mid.gmane.org/1284938514-16663-1-git-send-email-pclouds@gmail.com
One question to document experts: where to document "pathspec", git.txt?
Nguyễn Thái Ngọc Duy (5):
pathspec: mark wildcard pathspecs from the beginning
pathspec: add tree_recursive_diff parameter
tree_entry_interesting: turn to match_pathspec if wildcard is present
Convert ce_path_match() to use struct pathspec
ce_path_match: drop prefix matching in favor of match_pathspec
builtin/update-index.c | 8 ++++++--
cache.h | 5 ++++-
diff-lib.c | 10 ++++++++--
dir.c | 7 ++++++-
preload-index.c | 5 ++++-
read-cache.c | 25 ++-----------------------
revision.c | 5 ++++-
t/t4010-diff-pathspec.sh | 23 +++++++++++++++++++++++
tree-diff.c | 1 +
tree-walk.c | 18 ++++++++++++++++++
wt-status.c | 5 ++++-
11 files changed, 80 insertions(+), 32 deletions(-)
next reply other threads:[~2010-09-19 23:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-19 23:29 Nguyễn Thái Ngọc Duy [this message]
2010-09-19 23:29 ` [PATCH 1/5] pathspec: mark wildcard pathspecs from the beginning Nguyễn Thái Ngọc Duy
2010-09-19 23:29 ` [PATCH 2/5] pathspec: add tree_recursive_diff parameter Nguyễn Thái Ngọc Duy
2010-09-27 22:20 ` Junio C Hamano
2010-09-28 2:38 ` Nguyen Thai Ngoc Duy
2010-09-28 5:28 ` Junio C Hamano
2010-09-19 23:29 ` [PATCH 3/5] tree_entry_interesting: turn to match_pathspec if wildcard is present Nguyễn Thái Ngọc Duy
2010-09-19 23:29 ` [PATCH 4/5] Convert ce_path_match() to use struct pathspec Nguyễn Thái Ngọc Duy
2010-09-19 23:30 ` [PATCH 5/5] ce_path_match: drop prefix matching in favor of match_pathspec Nguyễn Thái Ngọc Duy
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=1284939000-16907-1-git-send-email-pclouds@gmail.com \
--to=pclouds@gmail.com \
--cc=git@vger.kernel.org \
/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).