2009/9/13 Jari Aalto <jari.aalto@xxxxxxxxx>: > Junio C Hamano <gitster@xxxxxxxxx> writes: > >> Jari Aalto <jari.aalto@xxxxxxxxx> writes: >> >>> --patch: >>> -p:: >>> In a modified work tree, choose interactively which patch hunks to >>> add. This gives a change to review the difference between the >>> index and the work before adding modified contents to the index. >> >> Sounds sensible. You may want to be even more direct and succinct, e.g. >> >> Interactively choose hunks of patch between the index and the work >> tree and add them to the index. > > Thanks, see below, > Jari > > From 63aa94e7782d6340ead0446ea80ed6223d7ac5c1 Mon Sep 17 00:00:00 2001 > From: Jari Aalto <jari.aalto@xxxxxxxxx> > Date: Sun, 13 Sep 2009 09:43:10 +0300 > Subject: [PATCH] Improve --patch option documentation in git-add > > Signed-off-by: Jari Aalto <jari.aalto@xxxxxxxxx> > --- > Documentation/git-add.txt | 11 ++++++++--- > 1 files changed, 8 insertions(+), 3 deletions(-) > > diff --git a/Documentation/git-add.txt b/Documentation/git-add.txt > index e67b7e8..b94fbec 100644 > --- a/Documentation/git-add.txt > +++ b/Documentation/git-add.txt > @@ -72,9 +72,14 @@ OPTIONS > > -p:: > --patch:: > - Similar to Interactive mode but the initial command loop is > - bypassed and the 'patch' subcommand is invoked using each of > - the specified filepatterns before exiting. > + Interactively choose hunks of patch between the index and the diff probably makes more sense than patch here > + work tree and add them to the index. This gives a change to a chance > + review the difference before adding modified contents to the differences? Not sure which I prefer on this one. > + index. > + > + This effectively runs ``add --interactive``, but bypass the bypasses > + initial command menu and directly jump to `patch` subcommand. jumps > + See ``Interactive mode'' for details. > > -e, \--edit:: > Open the diff vs. the index in an editor and let the user > -- > 1.6.3.3 -- Mikael Magnusson -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html