[PATCH 1/4] Refactor patch_update_cmd
- From
Wincent Colaiuta <win@wincent.com>
- Date
- Nov 21, 2007, 12:36 UTC
- Message-ID
- <1195648601-21736-2-git-send-email-win@wincent.com>
- In-Reply-To
- <1195648601-21736-1-git-send-email-win@wincent.com>
Split patch_update_cmd into two functions, one to prompt the user for a path to patch and another to do the actual work given that file path. This lays the groundwork for a future commit which will teach git-add--interactive to accept a path parameter and jump directly to the patch subcommand for that path, bypassing the interactive prompt.
Signed-off-by: Wincent Colaiuta <win@wincent.com> --- git-add--interactive.perl | 6 ++++-- 1 files changed, 4 insertions(+), 2 deletions(-)
diff --git a/git-add--interactive.perl b/git-add--interactive.perl index 0317ad9..fb1e92a 100755 --- a/git-add--interactive.perl +++ b/git-add--interactive.perl @@ -564,10 +564,12 @@ sub patch_update_cmd { IMMEDIATE => 1, HEADER => $status_head, }, @mods); - return if (!$it); + patch_update_file($it->{VALUE}) if ($it); +} +sub patch_update_file { my ($ix, $num); - my $path = $it->{VALUE}; + my $path = shift; my ($head, @hunk) = parse_diff($path); for (@{$head->{TEXT}}) { print;
-- 1.5.3.5.737.gdee1b