All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nanako Shiraishi <nanako3@lavabit.com>
To: Jari Aalto <jari.aalto@cante.net>
Cc: Sean Estabrooks <seanlkml@sympatico.ca>,
	Mikael Magnusson <mikachu@gmail.com>,
	git@vger.kernel.org
Subject: Re: [PATCH] Improve --patch option documentation in git-add (updated patch)
Date: Tue, 15 Sep 2009 15:52:08 +0900	[thread overview]
Message-ID: <20090915155208.6117@nanako3.lavabit.com> (raw)
In-Reply-To: <87fxaolqhd.fsf_-_@jondo.cante.net>

Quoting Jari Aalto <jari.aalto@cante.net>

> Sean Estabrooks <seanlkml@sympatico.ca> writes:
>> ... To me though, it seems more difficult to parse this description
>> than the one offered by Junio in an earlier thread ...perhaps you'd
>> consider something closer to yours, such as:
>>
>> 	Interactively review the differences between the index and the
>> 	work tree and choose which hunks to add into the index.
>>
>> 	This effectively runs ``add --interactive``, but bypasses the
>> 	initial command menu and jumps directly to the `patch` subcommand.
>> 	See ``Interactive mode'' for details.
>
>
> Updated, thanks,
> Jari
>
>
> From be5eebc53c2e3dcf67edfb371d8aa8263e1a8d69 Mon Sep 17 00:00:00 2001
> From: Jari Aalto <jari.aalto@cante.net>
> Date: Tue, 15 Sep 2009 08:33:51 +0300
> Subject: [PATCH] Improve --patch option documentation in git-add
>
> Signed-off-by: Jari Aalto <jari.aalto@cante.net>
> ---
>  Documentation/git-add.txt |    9 ++++++---
>  1 files changed, 6 insertions(+), 3 deletions(-)
>
> diff --git a/Documentation/git-add.txt b/Documentation/git-add.txt
> index e67b7e8..c57895a 100644
> --- a/Documentation/git-add.txt
> +++ b/Documentation/git-add.txt
> @@ -72,9 +72,12 @@ 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 review the differences between the index and the
> +	work tree and choose which hunks to add into the index.
> +
> +	This effectively runs ``add --interactive``, but bypasses the
> +	initial command menu and jumps directly to the `patch` subcommand.
> +	See ``Interactive mode'' for details.
>  
>  -e, \--edit::
>  	Open the diff vs. the index in an editor and let the user

Sorry, but this patch doesn't seem to apply anywhere. Have you fetched recently?

-- 
Nanako Shiraishi
http://ivory.ap.teacup.com/nanako3/

  reply	other threads:[~2009-09-15  6:53 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-30 17:29 [PATCH] Documentation/git-add.txt: Explain --patch option in layman terms Jari Aalto
2009-08-30 20:14 ` Junio C Hamano
2009-08-30 21:02   ` Jeff King
2009-08-30 21:56   ` Jari Aalto
2009-08-30 22:13     ` Junio C Hamano
2009-08-30 23:06       ` Jari Aalto
2009-08-30 23:20         ` Junio C Hamano
2009-08-31  7:46           ` Jari Aalto
2009-08-31 23:42             ` Junio C Hamano
2009-09-13  6:44               ` [PATCH] Improve --patch option documentation in git-add Jari Aalto
2009-09-13 13:48                 ` Mikael Magnusson
2009-09-13 14:09                   ` Jari Aalto
2009-09-14 13:13                     ` Sean Estabrooks
2009-09-15  5:35                       ` [PATCH] Improve --patch option documentation in git-add (updated patch) Jari Aalto
2009-09-15  6:52                         ` Nanako Shiraishi [this message]
2009-09-15  8:17                           ` Jari Aalto
2009-09-15 10:35                             ` Nanako Shiraishi
2009-08-30 23:31         ` [PATCH] Documentation/git-add.txt: Explain --patch option in layman terms Junio C Hamano
2009-08-31  7:06           ` Jari Aalto
2009-08-31  7:32             ` Junio C Hamano
2009-08-30 22:00   ` Jari Aalto

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=20090915155208.6117@nanako3.lavabit.com \
    --to=nanako3@lavabit.com \
    --cc=git@vger.kernel.org \
    --cc=jari.aalto@cante.net \
    --cc=mikachu@gmail.com \
    --cc=seanlkml@sympatico.ca \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.