From: Jeff King <peff@peff.net>
To: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
Cc: git@vger.kernel.org
Subject: [PATCH 3/5] add--interactive: allow hunk filtering on command line
Date: Wed, 27 Jul 2011 02:05:49 -0600 [thread overview]
Message-ID: <20110727080548.GC14002@sigill.intra.peff.net> (raw)
In-Reply-To: <20110727080303.GA8105@sigill.intra.peff.net>
If you have a lot of uninteresting hunks (e.g., because you
have a file with boilerplate that changed, but you want to
add only the interesting bits and discard the rest), it can
be cumbersome to sift through the boring hunks.
This patch provides an option to match hunks by regular
expression, pretending as if the non-matching changes do not
exist at all (similar to how path-limiting ignores
non-matching paths entirely).
There are two special case pseudo-hunks to consider in the
code: mode hunks and deletion hunks.
- If a filter is given, this patch will never include mode
hunks, since the user has asked for a specific subset of
hunks, and the mode has no text to match.
- Deletion hunks actually require no special care. In a
deletion there will be only a single giant diff hunk of
deleted content. If it matches the filter, then the
deletion can be presented as normal. If it doesn't
match, then we exit early from patch_update_file and
never consider showing the deletion at all (since there
is nothing to delete).
This patch provides only the perl portion; it is up to
individual callers of add--interactive to pass the option
through to the perl code.
Signed-off-by: Jeff King <peff@peff.net>
---
git-add--interactive.perl | 24 +++++++++++++++++++++++-
1 files changed, 23 insertions(+), 1 deletions(-)
diff --git a/git-add--interactive.perl b/git-add--interactive.perl
index 3e4c8a4..bb16f71 100755
--- a/git-add--interactive.perl
+++ b/git-add--interactive.perl
@@ -86,6 +86,7 @@ sub colored {
# command line options
my $patch_mode;
my $patch_mode_revision;
+my @patch_mode_hunk_filter;
sub apply_patch;
sub apply_patch_for_checkout_commit;
@@ -1273,17 +1274,33 @@ sub trim_error {
return $_;
}
+sub want_hunk {
+ my $hunk = shift;
+ my $text = join('', @{$hunk->{TEXT}});
+
+ foreach my $re (@patch_mode_hunk_filter) {
+ return 1 if $text =~ $re;
+ }
+ return 0;
+}
+
sub patch_update_file {
my $quit = 0;
my ($ix, $num);
my $path = shift;
my ($head, @hunk) = parse_diff($path);
+
+ if (@patch_mode_hunk_filter) {
+ @hunk = grep { want_hunk($_) } @hunk;
+ return unless @hunk;
+ }
+
($head, my $mode, my $deletion) = parse_diff_header($head);
for (@{$head->{DISPLAY}}) {
print;
}
- if (@{$mode->{TEXT}}) {
+ if (@{$mode->{TEXT}} && !@patch_mode_hunk_filter) {
unshift @hunk, $mode;
}
if (@{$deletion->{TEXT}}) {
@@ -1568,6 +1585,11 @@ sub process_args {
if ($ARGV[0] =~ /--patch(?:=(.*))?/) {
$patch_mode = defined $1 ? $1 : 'stage';
}
+ elsif ($ARGV[0] =~ /--hunk-filter=(.*)/) {
+ my $re = eval { qr{$1}m }
+ or die "malformed hunk filter $1: " . trim_error($@);
+ push @patch_mode_hunk_filter, $re;
+ }
else {
last;
}
--
1.7.5.4.31.ge4d5e
next prev parent reply other threads:[~2011-07-27 8:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-24 5:11 feature request: git add--interactive --patch on regex-matched hunks only Nguyen Thai Ngoc Duy
2011-07-25 21:55 ` Jeff King
2011-07-25 23:44 ` Junio C Hamano
2011-07-26 5:03 ` Jeff King
2011-07-26 3:03 ` Nguyen Thai Ngoc Duy
2011-07-26 5:14 ` Jeff King
2011-07-26 5:57 ` Nguyen Thai Ngoc Duy
2011-07-26 6:09 ` Jeff King
2011-07-26 12:44 ` Nguyen Thai Ngoc Duy
2011-07-26 13:03 ` Nguyen Thai Ngoc Duy
2011-07-27 8:10 ` Jeff King
2011-07-27 9:02 ` Nguyen Thai Ngoc Duy
2011-07-27 17:24 ` Jeff King
2011-07-27 8:03 ` Jeff King
2011-07-27 8:05 ` [PATCH 1/5] add--interactive: refactor patch mode argument processing Jeff King
2011-07-27 8:05 ` [PATCH 2/5] add--interactive: factor out regex error handling Jeff King
2011-07-27 8:05 ` Jeff King [this message]
2011-07-27 8:05 ` [PATCH 4/5] add--interactive: allow negatation of hunk filters Jeff King
2011-07-27 8:06 ` [PATCH 5/5] add--interactive: add option to autosplit hunks Jeff King
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=20110727080548.GC14002@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=pclouds@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 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).