From: Jared Hance <jaredhance@gmail.com>
To: git@vger.kernel.org
Subject: [PATCH/RFC v4 0/2] Add -e/--exclude to git clean.
Date: Tue, 20 Jul 2010 12:28:59 -0400 [thread overview]
Message-ID: <cover.1279643093.git.jaredhance@gmail.com> (raw)
In-Reply-To: <e257dd98b7493dcd72de9cf62d5847116e030ed0.1279564639.git.jaredhance@gmail.com>
This is the fourth round of patches for git clean -e.
This round introduces a test in t/t7300-clean.sh.
No other changes were added to builtin/clean.c or
Documentation/git-clean.txt.
Since this patch seems to be somewhat controversial, I've marked it as
PATCH/RFC. I would like some ideas on what to use for separators as
well as constructive critism on the Documentation and test.
Jared Hance (2):
Add --exclude to git-clean.
Add test for git clean -e.
Documentation/git-clean.txt | 7 ++++++-
builtin/clean.c | 21 +++++++++++++++++++++
t/t7300-clean.sh | 16 ++++++++++++++++
3 files changed, 43 insertions(+), 1 deletions(-)
next prev parent reply other threads:[~2010-07-20 16:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-19 15:50 [PATCH] Add --exclude to git-clean.j Jared Hance
2010-07-19 16:14 ` Jonathan Nieder
2010-07-19 16:21 ` Jared Hance
2010-07-19 16:18 ` [PATCH v2] Add --exclude to git-clean Jared Hance
2010-07-19 17:43 ` Junio C Hamano
2010-07-19 18:22 ` Jared Hance
2010-07-19 18:39 ` [PATCH v3] " Jared Hance
2010-07-20 16:28 ` Jared Hance [this message]
2010-07-20 16:29 ` [PATCH/RFC v4 1/2] " Jared Hance
2010-07-20 16:30 ` [PATCH 2/2] Add test for git clean -e Jared Hance
2010-07-20 17:03 ` [PATCH/RFC v4 0/2] Add -e/--exclude to git clean Aaron Crane
2010-07-20 17:13 ` Jared Hance
2010-07-20 18:02 ` Junio C Hamano
2010-07-20 18:23 ` Junio C Hamano
2010-07-20 19:11 ` Jared Hance
2010-09-23 9:05 ` Louis Strous
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=cover.1279643093.git.jaredhance@gmail.com \
--to=jaredhance@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).