{"thread":{"id":"27229","subject":"[PATCH] config.txt: interactive.singlekey is used by...","startedAt":"2011-04-30T14:54:01Z","lastAt":"2011-05-05T19:58:18Z","messageCount":23,"participants":["Valentin Haenel","Jeff King","Junio C Hamano"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"166800","messageId":"1304175241-30550-1-git-send-email-valentin.haenel@gmx.de","threadId":"27229","inReplyTo":null,"subject":"[PATCH] config.txt: interactive.singlekey is used by...","fromName":"Valentin Haenel","fromEmail":"valentin.haenel@gmx.de","sentAt":"2011-04-30T14:54:01Z","receivedAt":"2011-04-30T14:54:01Z","isPatch":true,"sender":{"key":"valentin.haenel@gmx.de","avatar":"https://avatars.githubusercontent.com/u/41563?v=4"},"body":"The config variable 'interactive.singlekey' influences also '--patch' mode of\ngit-stash and git-reset.\n\nSigned-off-by: Valentin Haenel <valentin.haenel@gmx.de>\n---\n\nPerhaps this incredibly useful setting should also be mentioned in manpages of\ngit-{add,reset.stash}?\n\nAre git-{add,reset.stash} the only commands that the setting influences?\n\n---\n Documentation/config.txt |    3 ++-\n 1 files changed, 2 insertions(+), 1 deletions(-)\n\ndiff --git a/Documentation/config.txt b/Documentation/config.txt\nindex 480dd0a..7dd9b01 100644\n--- a/Documentation/config.txt\n+++ b/Documentation/config.txt\n@@ -1297,7 +1297,8 @@ interactive.singlekey::\n \tIn interactive commands, allow the user to provide one-letter\n \tinput with a single key (i.e., without hitting enter).\n \tCurrently this is used only by the `\\--patch` mode of\n-\tlinkgit:git-add[1].  Note that this setting is silently\n+\tlinkgit:git-add[1], linkgit:git-reset[1] and linkgit:git-stash[1].\n+\tNote that this setting is silently\n \tignored if portable keystroke input is not available.\n \n log.date::\n-- \n1.7.1\n"},{"id":"166806","messageId":"20110501045140.GA13387@sigill.intra.peff.net","threadId":"27229","inReplyTo":"1304175241-30550-1-git-send-email-valentin.haenel@gmx.de","subject":"Re: [PATCH] config.txt: interactive.singlekey is used by...","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2011-05-01T04:51:40Z","receivedAt":"2011-05-01T04:51:40Z","isPatch":true,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Sat, Apr 30, 2011 at 04:54:01PM +0200, Valentin Haenel wrote:\n\n> Perhaps this incredibly useful setting should also be mentioned in manpages of\n> git-{add,reset.stash}?\n\nYeah, that would probably make sense.\n\n> Are git-{add,reset.stash} the only commands that the setting influences?\n\ngit-checkout also has a \"-p\" mode.\n\n-Peff\n"},{"id":"166866","messageId":"1304343872-1654-1-git-send-email-valentin.haenel@gmx.de","threadId":"27229","inReplyTo":"20110501045140.GA13387@sigill.intra.peff.net","subject":"[PATCH v2 0/5] better document 'interactive.singlekey'","fromName":"Valentin Haenel","fromEmail":"valentin.haenel@gmx.de","sentAt":"2011-05-02T13:44:27Z","receivedAt":"2011-05-02T13:44:27Z","isPatch":true,"sender":{"key":"valentin.haenel@gmx.de","avatar":"https://avatars.githubusercontent.com/u/41563?v=4"},"body":"The configuration 'interactive.singlekey' is incredibly useful but\nunderdocumentated. Bring the documentation in config.txt up-to-date and\ndocument it in individual commands.\n\nThanks to Jeff King for advice.\n\nValentin Haenel (5):\n  config.txt: 'interactive.singlekey; is used by...\n  git-add.txt: document 'interactive.singlekey'\n  git-reset.txt: document 'interactive.singlekey'\n  git-stash.txt: document 'interactive.singlekey'\n  git-checkout.txt: document 'interactive.singlekey'\n\n Documentation/config.txt       |    5 +++--\n Documentation/git-add.txt      |    3 +++\n Documentation/git-checkout.txt |    3 +++\n Documentation/git-reset.txt    |    3 +++\n Documentation/git-stash.txt    |    3 +++\n 5 files changed, 15 insertions(+), 2 deletions(-)\n"},{"id":"166867","messageId":"1304343872-1654-2-git-send-email-valentin.haenel@gmx.de","threadId":"27229","inReplyTo":"20110501045140.GA13387@sigill.intra.peff.net","subject":"[PATCH v2 1/5] config.txt: 'interactive.singlekey; is used by...","fromName":"Valentin Haenel","fromEmail":"valentin.haenel@gmx.de","sentAt":"2011-05-02T13:44:28Z","receivedAt":"2011-05-02T13:44:28Z","isPatch":true,"sender":{"key":"valentin.haenel@gmx.de","avatar":"https://avatars.githubusercontent.com/u/41563?v=4"},"body":"The config variable 'interactive.singlekey' influences also '--patch' mode of\ngit-add, git-reset, and git-checkout.\n\nSigned-off-by: Valentin Haenel <valentin.haenel@gmx.de>\nHelped-by: Jeff King <peff@peff.net>\n---\n Documentation/config.txt |    5 +++--\n 1 files changed, 3 insertions(+), 2 deletions(-)\n\ndiff --git a/Documentation/config.txt b/Documentation/config.txt\nindex 480dd0a..77e4f30 100644\n--- a/Documentation/config.txt\n+++ b/Documentation/config.txt\n@@ -1296,8 +1296,9 @@ instaweb.port::\n interactive.singlekey::\n \tIn interactive commands, allow the user to provide one-letter\n \tinput with a single key (i.e., without hitting enter).\n-\tCurrently this is used only by the `\\--patch` mode of\n-\tlinkgit:git-add[1].  Note that this setting is silently\n+\tCurrently this is used by the `\\--patch` mode of\n+\tlinkgit:git-add[1], linkgit:git-reset[1], linkgit:git-stash[1] and\n+\tlinkgit:git-checkout[1]. Note that this setting is silently\n \tignored if portable keystroke input is not available.\n \n log.date::\n-- \n1.7.1\n"},{"id":"166864","messageId":"1304343872-1654-3-git-send-email-valentin.haenel@gmx.de","threadId":"27229","inReplyTo":"20110501045140.GA13387@sigill.intra.peff.net","subject":"[PATCH v2 2/5] git-add.txt: document 'interactive.singlekey'","fromName":"Valentin Haenel","fromEmail":"valentin.haenel@gmx.de","sentAt":"2011-05-02T13:44:29Z","receivedAt":"2011-05-02T13:44:29Z","isPatch":true,"sender":{"key":"valentin.haenel@gmx.de","avatar":"https://avatars.githubusercontent.com/u/41563?v=4"},"body":"Signed-off-by: Valentin Haenel <valentin.haenel@gmx.de>\nHelped-by: Jeff King <peff@peff.net>\n---\n Documentation/git-add.txt |    3 +++\n 1 files changed, 3 insertions(+), 0 deletions(-)\n\ndiff --git a/Documentation/git-add.txt b/Documentation/git-add.txt\nindex 7eebbef..c172989 100644\n--- a/Documentation/git-add.txt\n+++ b/Documentation/git-add.txt\n@@ -86,6 +86,9 @@ OPTIONS\n This effectively runs `add --interactive`, but bypasses the\n initial command menu and directly jumps to the `patch` subcommand.\n See ``Interactive mode'' for details.\n++\n+The configuration `interactive.singlekey` allows the user to provide\n+one-letter input with a single key in this mode (i.e., without hitting enter).\n \n -e, \\--edit::\n \tOpen the diff vs. the index in an editor and let the user\n-- \n1.7.1\n"},{"id":"166865","messageId":"1304343872-1654-4-git-send-email-valentin.haenel@gmx.de","threadId":"27229","inReplyTo":"20110501045140.GA13387@sigill.intra.peff.net","subject":"[PATCH v2 3/5] git-reset.txt: document 'interactive.singlekey'","fromName":"Valentin Haenel","fromEmail":"valentin.haenel@gmx.de","sentAt":"2011-05-02T13:44:30Z","receivedAt":"2011-05-02T13:44:30Z","isPatch":true,"sender":{"key":"valentin.haenel@gmx.de","avatar":"https://avatars.githubusercontent.com/u/41563?v=4"},"body":"Signed-off-by: Valentin Haenel <valentin.haenel@gmx.de>\nHelped-by: Jeff King <peff@peff.net>\n---\n Documentation/git-reset.txt |    3 +++\n 1 files changed, 3 insertions(+), 0 deletions(-)\n\ndiff --git a/Documentation/git-reset.txt b/Documentation/git-reset.txt\nindex 8481f9d..9f073d3 100644\n--- a/Documentation/git-reset.txt\n+++ b/Documentation/git-reset.txt\n@@ -41,6 +41,9 @@ working tree in one go.\n +\n This means that `git reset -p` is the opposite of `git add -p` (see\n linkgit:git-add[1]).\n++\n+The configuration `interactive.singlekey` allows the user to provide\n+one-letter input with a single key in this mode (i.e., without hitting enter).\n \n 'git reset' [--<mode>] [<commit>]::\n \tThis form resets the current branch head to <commit> and\n-- \n1.7.1\n"},{"id":"166863","messageId":"1304343872-1654-5-git-send-email-valentin.haenel@gmx.de","threadId":"27229","inReplyTo":"20110501045140.GA13387@sigill.intra.peff.net","subject":"[PATCH v2 4/5] git-stash.txt: document 'interactive.singlekey'","fromName":"Valentin Haenel","fromEmail":"valentin.haenel@gmx.de","sentAt":"2011-05-02T13:44:31Z","receivedAt":"2011-05-02T13:44:31Z","isPatch":true,"sender":{"key":"valentin.haenel@gmx.de","avatar":"https://avatars.githubusercontent.com/u/41563?v=4"},"body":"Signed-off-by: Valentin Haenel <valentin.haenel@gmx.de>\nHelped-by: Jeff King <peff@peff.net>\n---\n Documentation/git-stash.txt |    3 +++\n 1 files changed, 3 insertions(+), 0 deletions(-)\n\ndiff --git a/Documentation/git-stash.txt b/Documentation/git-stash.txt\nindex 79abc38..c8a349e 100644\n--- a/Documentation/git-stash.txt\n+++ b/Documentation/git-stash.txt\n@@ -63,6 +63,9 @@ from your worktree.\n +\n The `--patch` option implies `--keep-index`.  You can use\n `--no-keep-index` to override this.\n++\n+The configuration `interactive.singlekey` allows the user to provide\n+one-letter input with a single key when using `--patch` (i.e., without hitting enter).\n \n list [<options>]::\n \n-- \n1.7.1\n"},{"id":"166868","messageId":"1304343872-1654-6-git-send-email-valentin.haenel@gmx.de","threadId":"27229","inReplyTo":"20110501045140.GA13387@sigill.intra.peff.net","subject":"[PATCH v2 5/5] git-checkout.txt: document 'interactive.singlekey'","fromName":"Valentin Haenel","fromEmail":"valentin.haenel@gmx.de","sentAt":"2011-05-02T13:44:32Z","receivedAt":"2011-05-02T13:44:32Z","isPatch":true,"sender":{"key":"valentin.haenel@gmx.de","avatar":"https://avatars.githubusercontent.com/u/41563?v=4"},"body":"Signed-off-by: Valentin Haenel <valentin.haenel@gmx.de>\nHelped-by: Jeff King <peff@peff.net>\n---\n Documentation/git-checkout.txt |    3 +++\n 1 files changed, 3 insertions(+), 0 deletions(-)\n\ndiff --git a/Documentation/git-checkout.txt b/Documentation/git-checkout.txt\nindex 1063f69..556c82b 100644\n--- a/Documentation/git-checkout.txt\n+++ b/Documentation/git-checkout.txt\n@@ -63,6 +63,9 @@ Using `-f` will ignore these unmerged entries.  The contents from a\n specific side of the merge can be checked out of the index by\n using `--ours` or `--theirs`.  With `-m`, changes made to the working tree\n file can be discarded to re-create the original conflicted merge result.\n++\n+The configuration `interactive.singlekey` allows the user to provide\n+one-letter input with a single key when using `--patch` (i.e., without hitting enter).\n \n OPTIONS\n -------\n-- \n1.7.1\n"},{"id":"166884","messageId":"7v1v0hngs9.fsf@alter.siamese.dyndns.org","threadId":"27229","inReplyTo":"1304343872-1654-3-git-send-email-valentin.haenel@gmx.de","subject":"Re: [PATCH v2 2/5] git-add.txt: document 'interactive.singlekey'","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2011-05-02T17:22:04Z","receivedAt":"2011-05-02T17:22:04Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Valentin Haenel <valentin.haenel@gmx.de> writes:\n\n> Signed-off-by: Valentin Haenel <valentin.haenel@gmx.de>\n> Helped-by: Jeff King <peff@peff.net>\n> ---\n>  Documentation/git-add.txt |    3 +++\n>  1 files changed, 3 insertions(+), 0 deletions(-)\n>\n> diff --git a/Documentation/git-add.txt b/Documentation/git-add.txt\n> index 7eebbef..c172989 100644\n> --- a/Documentation/git-add.txt\n> +++ b/Documentation/git-add.txt\n> @@ -86,6 +86,9 @@ OPTIONS\n>  This effectively runs `add --interactive`, but bypasses the\n>  initial command menu and directly jumps to the `patch` subcommand.\n>  See ``Interactive mode'' for details.\n> ++\n> +The configuration `interactive.singlekey` allows the user to provide\n> +one-letter input with a single key in this mode (i.e., without hitting enter).\n\nI do not think this belongs here.  For one thing, as the text in the\npre-context in your patch says, this also applies to \"-i\".  Since they\nboth refer to the \"Interactive mode\" section for further details, I think\nthat would be more appropriate place to mention the variable, which after\nall is a tiny part of the detail (think: if somebody does not know how to\noperate the interactive mode, \"singlekey does not require enter\" is not\nvery helpful).\n\nNot all the configuration variables \"git-add\" pays attention to are\nmentioned in this manual page (e.g. color.interactive.<slot> and\nadd.ignoreerrors are not mentioned).  I also do not think duplicating\neverything \"git add\" pays attention to in this manual page is necessarily\na good thing.  I'd prefer to mention only the important ones (e.g. the\nones that give default values for their corresponding command line\noptions) in the main part of the documentation.\n\nFor the other commands that internally invoke \"add -p\", the text before\nyour patch is unhelpful to people who have not seen \"git add -p\" in\naction.  Some of them do not even mention where the interactive mode is\nexplained.  The result of your patch does not help the situation, and\nabruptly start talking about interactive.singlekey, still without teaching\nhow to operate the interactive mode at all.\n\nI think the end result of the series should look something like this patch,\nafter applying your [PATCH 1/5], but discarding 2 thru 5.\n\n\n Documentation/git-add.txt      |    5 ++++-\n Documentation/git-checkout.txt |    4 +++-\n Documentation/git-reset.txt    |    4 +++-\n Documentation/git-stash.txt    |    4 +++-\n 4 files changed, 13 insertions(+), 4 deletions(-)\n\ndiff --git a/Documentation/git-add.txt b/Documentation/git-add.txt\nindex 7eebbef..27e0160 100644\n--- a/Documentation/git-add.txt\n+++ b/Documentation/git-add.txt\n@@ -134,6 +134,8 @@ subdirectories.\n \tIf some files could not be added because of errors indexing\n \tthem, do not abort the operation, but continue adding the\n \tothers. The command shall still exit with non-zero status.\n+\tThe configuration variable `add.ignoreErrors` can be set to\n+\ttrue to make this the default behaviour.\n \n --ignore-missing::\n \tThis option can only be used together with --dry-run. By using\n@@ -189,7 +191,8 @@ interactive command loop.\n The command loop shows the list of subcommands available, and\n gives a prompt \"What now> \".  In general, when the prompt ends\n with a single '>', you can pick only one of the choices given\n-and type return, like this:\n+and type return (the configuration variable `interactive.singlekey`\n+can be set to true to omit hitting return, by the way), like this:\n \n ------------\n     *** Commands ***\ndiff --git a/Documentation/git-checkout.txt b/Documentation/git-checkout.txt\nindex 1063f69..7c58028 100644\n--- a/Documentation/git-checkout.txt\n+++ b/Documentation/git-checkout.txt\n@@ -179,7 +179,9 @@ the conflicted merge in the specified paths.\n --patch::\n \tInteractively select hunks in the difference between the\n \t<tree-ish> (or the index, if unspecified) and the working\n-\ttree.  The chosen hunks are then applied in reverse to the\n+\ttree (see the ``Interactive Mode`` section of gitlink:git-add[1]\n+\tto learn how to operate the interactive mode).  The chosen\n+\thunks are then applied in reverse to the\n \tworking tree (and if a <tree-ish> was specified, the index).\n +\n This means that you can use `git checkout -p` to selectively discard\ndiff --git a/Documentation/git-reset.txt b/Documentation/git-reset.txt\nindex 8481f9d..37f487e 100644\n--- a/Documentation/git-reset.txt\n+++ b/Documentation/git-reset.txt\n@@ -36,7 +36,9 @@ working tree in one go.\n \n 'git reset' --patch|-p [<commit>] [--] [<paths>...]::\n \tInteractively select hunks in the difference between the index\n-\tand <commit> (defaults to HEAD).  The chosen hunks are applied\n+\tand <commit> (see the ``Interactive Mode``\n+\tsection of gitlink:git-add[1] to learn how to operate the interactive\n+\tmode).  Missing <commit> defaults to HEAD.  The chosen hunks are applied\n \tin reverse to the index.\n +\n This means that `git reset -p` is the opposite of `git add -p` (see\ndiff --git a/Documentation/git-stash.txt b/Documentation/git-stash.txt\nindex 79abc38..281bd35 100644\n--- a/Documentation/git-stash.txt\n+++ b/Documentation/git-stash.txt\n@@ -55,7 +55,9 @@ If the `--keep-index` option is used, all changes already added to the\n index are left intact.\n +\n With `--patch`, you can interactively select hunks from in the diff\n-between HEAD and the working tree to be stashed.  The stash entry is\n+between HEAD and the working tree to be stashed (see the ``Interactive Mode``\n+section of gitlink:git-add[1] to learn how to operate the interactive\n+mode).  The stash entry is\n constructed such that its index state is the same as the index state\n of your repository, and its worktree contains only the changes you\n selected interactively.  The selected changes are then rolled back\n"},{"id":"166939","messageId":"20110503153857.GC2211@kudu.in-berlin.de","threadId":"27229","inReplyTo":"7v1v0hngs9.fsf@alter.siamese.dyndns.org","subject":"Re: [PATCH v2 2/5] git-add.txt: document 'interactive.singlekey'","fromName":"Valentin Haenel","fromEmail":"valentin.haenel@gmx.de","sentAt":"2011-05-03T15:38:57Z","receivedAt":"2011-05-03T15:38:57Z","isPatch":true,"sender":{"key":"valentin.haenel@gmx.de","avatar":"https://avatars.githubusercontent.com/u/41563?v=4"},"body":"Hi,\n\nthanks for the feedback. I have some remaining questions, see below.\n\n* Junio C Hamano <gitster@pobox.com> [110502]:\n> Valentin Haenel <valentin.haenel@gmx.de> writes:\n> \n> > Signed-off-by: Valentin Haenel <valentin.haenel@gmx.de>\n> > Helped-by: Jeff King <peff@peff.net>\n> > ---\n> >  Documentation/git-add.txt |    3 +++\n> >  1 files changed, 3 insertions(+), 0 deletions(-)\n> >\n> > diff --git a/Documentation/git-add.txt b/Documentation/git-add.txt\n> > index 7eebbef..c172989 100644\n> > --- a/Documentation/git-add.txt\n> > +++ b/Documentation/git-add.txt\n> > @@ -86,6 +86,9 @@ OPTIONS\n> >  This effectively runs `add --interactive`, but bypasses the\n> >  initial command menu and directly jumps to the `patch` subcommand.\n> >  See ``Interactive mode'' for details.\n> > ++\n> > +The configuration `interactive.singlekey` allows the user to provide\n> > +one-letter input with a single key in this mode (i.e., without hitting enter).\n> \n> I do not think this belongs here.  For one thing, as the text in the\n> pre-context in your patch says, this also applies to \"-i\".  Since they\n> both refer to the \"Interactive mode\" section for further details, I think\n> that would be more appropriate place to mention the variable, which after\n> all is a tiny part of the detail (think: if somebody does not know how to\n> operate the interactive mode, \"singlekey does not require enter\" is not\n> very helpful).\n\nI agree that details should go into the section \"Interactive Mode\". \n\nHowever, it would seem that the configuration influences only the\npatch mode of the interactive mode (unless i am missing something).\nI just tried to naviagte the menu i get with 'git add -i' and typing the\nenter was required. (Using 1.7.5) This would affect the positioning of\nthe addition, see below.\n\n> Not all the configuration variables \"git-add\" pays attention to are\n> mentioned in this manual page (e.g. color.interactive.<slot> and\n> add.ignoreerrors are not mentioned).  I also do not think duplicating\n> everything \"git add\" pays attention to in this manual page is necessarily\n> a good thing.  I'd prefer to mention only the important ones (e.g. the\n> ones that give default values for their corresponding command line\n> options) in the main part of the documentation.\n> \n> For the other commands that internally invoke \"add -p\", the text before\n> your patch is unhelpful to people who have not seen \"git add -p\" in\n> action.  Some of them do not even mention where the interactive mode is\n> explained.  The result of your patch does not help the situation, and\n> abruptly start talking about interactive.singlekey, still without teaching\n> how to operate the interactive mode at all.\n\nYeah, I agree.\n\n> I think the end result of the series should look something like this patch,\n> after applying your [PATCH 1/5], but discarding 2 thru 5.\n> \n> \n>  Documentation/git-add.txt      |    5 ++++-\n>  Documentation/git-checkout.txt |    4 +++-\n>  Documentation/git-reset.txt    |    4 +++-\n>  Documentation/git-stash.txt    |    4 +++-\n>  4 files changed, 13 insertions(+), 4 deletions(-)\n> \n> diff --git a/Documentation/git-add.txt b/Documentation/git-add.txt\n> index 7eebbef..27e0160 100644\n> --- a/Documentation/git-add.txt\n> +++ b/Documentation/git-add.txt\n> @@ -134,6 +134,8 @@ subdirectories.\n>  \tIf some files could not be added because of errors indexing\n>  \tthem, do not abort the operation, but continue adding the\n>  \tothers. The command shall still exit with non-zero status.\n> +\tThe configuration variable `add.ignoreErrors` can be set to\n> +\ttrue to make this the default behaviour.\n\nIts unrelated to 'interactive.singlekey', can i 'stuff' it into the\nseries too, or better make a seperate one?\n\n>  \n>  --ignore-missing::\n>  \tThis option can only be used together with --dry-run. By using\n> @@ -189,7 +191,8 @@ interactive command loop.\n>  The command loop shows the list of subcommands available, and\n>  gives a prompt \"What now> \".  In general, when the prompt ends\n>  with a single '>', you can pick only one of the choices given\n> -and type return, like this:\n> +and type return (the configuration variable `interactive.singlekey`\n> +can be set to true to omit hitting return, by the way), like this:\n\nIf what i wrote above is correct, this should go into the section about\nthe patch mode, rather than here?\n\n>  ------------\n>      *** Commands ***\n> diff --git a/Documentation/git-checkout.txt b/Documentation/git-checkout.txt\n> index 1063f69..7c58028 100644\n> --- a/Documentation/git-checkout.txt\n> +++ b/Documentation/git-checkout.txt\n> @@ -179,7 +179,9 @@ the conflicted merge in the specified paths.\n>  --patch::\n>  \tInteractively select hunks in the difference between the\n>  \t<tree-ish> (or the index, if unspecified) and the working\n> -\ttree.  The chosen hunks are then applied in reverse to the\n> +\ttree (see the ``Interactive Mode`` section of gitlink:git-add[1]\n> +\tto learn how to operate the interactive mode).  The chosen\n> +\thunks are then applied in reverse to the\n>  \tworking tree (and if a <tree-ish> was specified, the index).\n>  +\n>  This means that you can use `git checkout -p` to selectively discard\n> diff --git a/Documentation/git-reset.txt b/Documentation/git-reset.txt\n> index 8481f9d..37f487e 100644\n> --- a/Documentation/git-reset.txt\n> +++ b/Documentation/git-reset.txt\n> @@ -36,7 +36,9 @@ working tree in one go.\n>  \n>  'git reset' --patch|-p [<commit>] [--] [<paths>...]::\n>  \tInteractively select hunks in the difference between the index\n> -\tand <commit> (defaults to HEAD).  The chosen hunks are applied\n> +\tand <commit> (see the ``Interactive Mode``\n> +\tsection of gitlink:git-add[1] to learn how to operate the interactive\n> +\tmode).  Missing <commit> defaults to HEAD.  The chosen hunks are applied\n>  \tin reverse to the index.\n>  +\n>  This means that `git reset -p` is the opposite of `git add -p` (see\n> diff --git a/Documentation/git-stash.txt b/Documentation/git-stash.txt\n> index 79abc38..281bd35 100644\n> --- a/Documentation/git-stash.txt\n> +++ b/Documentation/git-stash.txt\n> @@ -55,7 +55,9 @@ If the `--keep-index` option is used, all changes already added to the\n>  index are left intact.\n>  +\n>  With `--patch`, you can interactively select hunks from in the diff\n> -between HEAD and the working tree to be stashed.  The stash entry is\n> +between HEAD and the working tree to be stashed (see the ``Interactive Mode``\n> +section of gitlink:git-add[1] to learn how to operate the interactive\n> +mode).  The stash entry is\n>  constructed such that its index state is the same as the index state\n>  of your repository, and its worktree contains only the changes you\n>  selected interactively.  The selected changes are then rolled back\n"},{"id":"166959","messageId":"7vbozjipmp.fsf@alter.siamese.dyndns.org","threadId":"27229","inReplyTo":"20110503153857.GC2211@kudu.in-berlin.de","subject":"Re: [PATCH v2 2/5] git-add.txt: document 'interactive.singlekey'","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2011-05-03T18:51:42Z","receivedAt":"2011-05-03T18:51:42Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Valentin Haenel <valentin.haenel@gmx.de> writes:\n\n>>  \tIf some files could not be added because of errors indexing\n>>  \tthem, do not abort the operation, but continue adding the\n>>  \tothers. The command shall still exit with non-zero status.\n>> +\tThe configuration variable `add.ignoreErrors` can be set to\n>> +\ttrue to make this the default behaviour.\n>\n> Its unrelated to 'interactive.singlekey', can i 'stuff' it into the\n> series too, or better make a seperate one?\n\nYes, this is totally unrelated; I just wanted to write it down so somebody\nremembers.  Please make it a separate patch that comes before anything\nelse.\n\n>> @@ -189,7 +191,8 @@ interactive command loop.\n>>  The command loop shows the list of subcommands available, and\n>>  gives a prompt \"What now> \".  In general, when the prompt ends\n>>  with a single '>', you can pick only one of the choices given\n>> -and type return, like this:\n>> +and type return (the configuration variable `interactive.singlekey`\n>> +can be set to true to omit hitting return, by the way), like this:\n>\n> If what i wrote above is correct, this should go into the section about\n> the patch mode, rather than here?\n\nYes, please move find a more appropriate home for that description.\n\nThanks.\n"},{"id":"167041","messageId":"20110504195817.GL2211@kudu.in-berlin.de","threadId":"27229","inReplyTo":"7vbozjipmp.fsf@alter.siamese.dyndns.org","subject":"[PATCH] git-add.txt: document 'add.ignoreErrors'","fromName":"Valentin Haenel","fromEmail":"valentin.haenel@gmx.de","sentAt":"2011-05-04T19:58:17Z","receivedAt":"2011-05-04T19:58:17Z","isPatch":true,"sender":{"key":"valentin.haenel@gmx.de","avatar":"https://avatars.githubusercontent.com/u/41563?v=4"},"body":"Signed-off-by: Valentin Haenel <valentin.haenel@gmx.de>\nNoticed-by: Junio C Hamano <gitster@pobox.com>\n---\n\n* Junio C Hamano <gitster@pobox.com> [110503]:\n> Valentin Haenel <valentin.haenel@gmx.de> writes:\n> >>  \tIf some files could not be added because of errors indexing\n> >>  \tthem, do not abort the operation, but continue adding the\n> >>  \tothers. The command shall still exit with non-zero status.\n> >> +\tThe configuration variable `add.ignoreErrors` can be set to\n> >> +\ttrue to make this the default behaviour.\n> >\n> > Its unrelated to 'interactive.singlekey', can i 'stuff' it into the\n> > series too, or better make a seperate one?\n> \n> Yes, this is totally unrelated; I just wanted to write it down so somebody\n> remembers.  Please make it a separate patch that comes before anything\n> else.\n\nhere you go.\n\n Documentation/git-add.txt |    2 ++\n 1 files changed, 2 insertions(+), 0 deletions(-)\n\ndiff --git a/Documentation/git-add.txt b/Documentation/git-add.txt\nindex 7eebbef..35cb5d3 100644\n--- a/Documentation/git-add.txt\n+++ b/Documentation/git-add.txt\n@@ -134,6 +134,8 @@ subdirectories.\n \tIf some files could not be added because of errors indexing\n \tthem, do not abort the operation, but continue adding the\n \tothers. The command shall still exit with non-zero status.\n+\tThe configuration variable `add.ignoreErrors` can be set to\n+\ttrue to make this the default behaviour.\n \n --ignore-missing::\n \tThis option can only be used together with --dry-run. By using\n-- \n1.7.1\n"},{"id":"167145","messageId":"1304621271-17107-1-git-send-email-valentin.haenel@gmx.de","threadId":"27229","inReplyTo":"7vbozjipmp.fsf@alter.siamese.dyndns.org","subject":"[PATCH v3 0/5] better document 'interactive.singlekey' and '--patch'","fromName":"Valentin Haenel","fromEmail":"valentin.haenel@gmx.de","sentAt":"2011-05-05T18:47:51Z","receivedAt":"2011-05-05T18:47:51Z","isPatch":true,"sender":{"key":"valentin.haenel@gmx.de","avatar":"https://avatars.githubusercontent.com/u/41563?v=4"},"body":"This is round 3 of this series. Now improves the documentation of\n'--patch' in various manpages in addition to better documenting\n'interactive.singlekey' in config.txt and git-add.txt.\n\nFirst patch brings the documentation in config.txt up-to-date. The\nsecond patch documents the configuration in git-add manpage. The last\nthree patches improve the documentation for '--patch' in manpages of\ngit-checkout, git-reset and git-stash. Updating the synopsis in each\none, adding a link to the git-add manpage where the interactive\n'--patch'-mode & 'interactive.singlekey' are described, and improving\nthe description for that option.\n\nNote that the first patch is already included in pu (93556471), but I\nincluded it here again since its part of the series. Is that the right\nthing to do, or could I have dropped it?\n\nThanks to Peff and Junio for comments and advice.\n\nV-\n\nValentin Haenel (5):\n  config.txt: 'interactive.singlekey; is used by...\n  git-add.txt: document 'interactive.singlekey'\n  git-reset.txt: better docs for '--patch'\n  git-stash.txt: better docs for '--patch'\n  git-checkout.txt: better docs for '--patch'\n\n Documentation/config.txt       |    5 +++--\n Documentation/git-add.txt      |    6 +++++-\n Documentation/git-checkout.txt |    7 ++++---\n Documentation/git-reset.txt    |    7 ++++---\n Documentation/git-stash.txt    |    9 +++++----\n 5 files changed, 21 insertions(+), 13 deletions(-)\n"},{"id":"167149","messageId":"1304621328-17184-1-git-send-email-valentin.haenel@gmx.de","threadId":"27229","inReplyTo":"1304621271-17107-1-git-send-email-valentin.haenel@gmx.de","subject":"[PATCH v3 1/5] config.txt: 'interactive.singlekey; is used by...","fromName":"Valentin Haenel","fromEmail":"valentin.haenel@gmx.de","sentAt":"2011-05-05T18:48:44Z","receivedAt":"2011-05-05T18:48:44Z","isPatch":true,"sender":{"key":"valentin.haenel@gmx.de","avatar":"https://avatars.githubusercontent.com/u/41563?v=4"},"body":"The config variable 'interactive.singlekey' influences also '--patch' mode of\ngit-add, git-reset, and git-checkout.\n\nSigned-off-by: Valentin Haenel <valentin.haenel@gmx.de>\nHelped-by: Jeff King <peff@peff.net>\n---\n Documentation/config.txt |    5 +++--\n 1 files changed, 3 insertions(+), 2 deletions(-)\n\ndiff --git a/Documentation/config.txt b/Documentation/config.txt\nindex 480dd0a..77e4f30 100644\n--- a/Documentation/config.txt\n+++ b/Documentation/config.txt\n@@ -1296,8 +1296,9 @@ instaweb.port::\n interactive.singlekey::\n \tIn interactive commands, allow the user to provide one-letter\n \tinput with a single key (i.e., without hitting enter).\n-\tCurrently this is used only by the `\\--patch` mode of\n-\tlinkgit:git-add[1].  Note that this setting is silently\n+\tCurrently this is used by the `\\--patch` mode of\n+\tlinkgit:git-add[1], linkgit:git-reset[1], linkgit:git-stash[1] and\n+\tlinkgit:git-checkout[1]. Note that this setting is silently\n \tignored if portable keystroke input is not available.\n \n log.date::\n-- \n1.7.1\n"},{"id":"167146","messageId":"1304621328-17184-2-git-send-email-valentin.haenel@gmx.de","threadId":"27229","inReplyTo":"1304621271-17107-1-git-send-email-valentin.haenel@gmx.de","subject":"[PATCH v3 2/5] git-add.txt: document 'interactive.singlekey'","fromName":"Valentin Haenel","fromEmail":"valentin.haenel@gmx.de","sentAt":"2011-05-05T18:48:45Z","receivedAt":"2011-05-05T18:48:45Z","isPatch":true,"sender":{"key":"valentin.haenel@gmx.de","avatar":"https://avatars.githubusercontent.com/u/41563?v=4"},"body":"This is documented in the section about the 'Interactive Mode', rather than for\nthe option '--patch', since this is the section is where people go to learn\nabout '--patch'.\n\nSigned-off-by: Valentin Haenel <valentin.haenel@gmx.de>\nHelped-by: Jeff King <peff@peff.net>\nMentored-by: Junio C Hamano <gitster@pobox.com>\n---\n Documentation/git-add.txt |    6 +++++-\n 1 files changed, 5 insertions(+), 1 deletions(-)\n\ndiff --git a/Documentation/git-add.txt b/Documentation/git-add.txt\nindex 35cb5d3..9c1d395 100644\n--- a/Documentation/git-add.txt\n+++ b/Documentation/git-add.txt\n@@ -274,7 +274,8 @@ patch::\n   This lets you choose one path out of a 'status' like selection.\n   After choosing the path, it presents the diff between the index\n   and the working tree file and asks you if you want to stage\n-  the change of each hunk.  You can say:\n+  the change of each hunk.  You can select one of the following\n+  options and type return:\n \n        y - stage this hunk\n        n - do not stage this hunk\n@@ -293,6 +294,9 @@ patch::\n +\n After deciding the fate for all hunks, if there is any hunk\n that was chosen, the index is updated with the selected hunks.\n++\n+You can omit having to type return here, by setting the configuration\n+variable `interactive.singlekey` to `true`.\n \n diff::\n \n-- \n1.7.1\n"},{"id":"167152","messageId":"1304621328-17184-3-git-send-email-valentin.haenel@gmx.de","threadId":"27229","inReplyTo":"1304621271-17107-1-git-send-email-valentin.haenel@gmx.de","subject":"[PATCH v3 3/5] git-reset.txt: better docs for '--patch'","fromName":"Valentin Haenel","fromEmail":"valentin.haenel@gmx.de","sentAt":"2011-05-05T18:48:46Z","receivedAt":"2011-05-05T18:48:46Z","isPatch":true,"sender":{"key":"valentin.haenel@gmx.de","avatar":"https://avatars.githubusercontent.com/u/41563?v=4"},"body":"* Include '-p' in the synopsis.\n* Include a better wording for what 'git reset -p' does.\n  (interactively unstage hunks)\n* Include a link to the git-add manpage for a description of the patch-mode.\n\nSigned-off-by: Valentin Haenel <valentin.haenel@gmx.de>\nHelped-by: Jeff King <peff@peff.net>\nMentored-by: Junio C Hamano <gitster@pobox.com>\n---\n Documentation/git-reset.txt |    7 ++++---\n 1 files changed, 4 insertions(+), 3 deletions(-)\n\ndiff --git a/Documentation/git-reset.txt b/Documentation/git-reset.txt\nindex 8481f9d..b6ed0c7 100644\n--- a/Documentation/git-reset.txt\n+++ b/Documentation/git-reset.txt\n@@ -9,7 +9,7 @@ SYNOPSIS\n --------\n [verse]\n 'git reset' [-q] [<commit>] [--] <paths>...\n-'git reset' --patch [<commit>] [--] [<paths>...]\n+'git reset' --patch|-p [<commit>] [--] [<paths>...]\n 'git reset' [--soft | --mixed | --hard | --merge | --keep] [-q] [<commit>]\n \n DESCRIPTION\n@@ -39,8 +39,9 @@ working tree in one go.\n \tand <commit> (defaults to HEAD).  The chosen hunks are applied\n \tin reverse to the index.\n +\n-This means that `git reset -p` is the opposite of `git add -p` (see\n-linkgit:git-add[1]).\n+This means that `git reset -p` is the opposite of `git add -p`, i.e.\n+you can use it to selectively unstage hunks. See the ``Interactive Mode''\n+section of linkgit:git-add[1] to learn how to operate the `\\--patch` mode.\n \n 'git reset' [--<mode>] [<commit>]::\n \tThis form resets the current branch head to <commit> and\n-- \n1.7.1\n"},{"id":"167147","messageId":"1304621328-17184-4-git-send-email-valentin.haenel@gmx.de","threadId":"27229","inReplyTo":"1304621271-17107-1-git-send-email-valentin.haenel@gmx.de","subject":"[PATCH v3 4/5] git-stash.txt: better docs for '--patch'","fromName":"Valentin Haenel","fromEmail":"valentin.haenel@gmx.de","sentAt":"2011-05-05T18:48:47Z","receivedAt":"2011-05-05T18:48:47Z","isPatch":true,"sender":{"key":"valentin.haenel@gmx.de","avatar":"https://avatars.githubusercontent.com/u/41563?v=4"},"body":"* Include '-p' in synopsis and options.\n* Fix a typo.\n* Include a link to the git-add manpage for a description of the patch-mode.\n\nSigned-off-by: Valentin Haenel <valentin.haenel@gmx.de>\nHelped-by: Jeff King <peff@peff.net>\nMentored-by: Junio C Hamano <gitster@pobox.com>\n---\n Documentation/git-stash.txt |    9 +++++----\n 1 files changed, 5 insertions(+), 4 deletions(-)\n\ndiff --git a/Documentation/git-stash.txt b/Documentation/git-stash.txt\nindex 79abc38..15f051f 100644\n--- a/Documentation/git-stash.txt\n+++ b/Documentation/git-stash.txt\n@@ -13,7 +13,7 @@ SYNOPSIS\n 'git stash' drop [-q|--quiet] [<stash>]\n 'git stash' ( pop | apply ) [--index] [-q|--quiet] [<stash>]\n 'git stash' branch <branchname> [<stash>]\n-'git stash' [save [--patch] [-k|--[no-]keep-index] [-q|--quiet] [<message>]]\n+'git stash' [save [-p|--patch] [-k|--[no-]keep-index] [-q|--quiet] [<message>]]\n 'git stash' clear\n 'git stash' create\n \n@@ -42,7 +42,7 @@ is also possible).\n OPTIONS\n -------\n \n-save [--patch] [--[no-]keep-index] [-q|--quiet] [<message>]::\n+save [-p|--patch] [--[no-]keep-index] [-q|--quiet] [<message>]::\n \n \tSave your local modifications to a new 'stash', and run `git reset\n \t--hard` to revert them.  The <message> part is optional and gives\n@@ -54,12 +54,13 @@ save [--patch] [--[no-]keep-index] [-q|--quiet] [<message>]::\n If the `--keep-index` option is used, all changes already added to the\n index are left intact.\n +\n-With `--patch`, you can interactively select hunks from in the diff\n+With `--patch`, you can interactively select hunks from the diff\n between HEAD and the working tree to be stashed.  The stash entry is\n constructed such that its index state is the same as the index state\n of your repository, and its worktree contains only the changes you\n selected interactively.  The selected changes are then rolled back\n-from your worktree.\n+from your worktree. See the ``Interactive Mode'' section of\n+linkgit:git-add[1] to learn how to operate the `\\--patch` mode.\n +\n The `--patch` option implies `--keep-index`.  You can use\n `--no-keep-index` to override this.\n-- \n1.7.1\n"},{"id":"167148","messageId":"1304621328-17184-5-git-send-email-valentin.haenel@gmx.de","threadId":"27229","inReplyTo":"1304621271-17107-1-git-send-email-valentin.haenel@gmx.de","subject":"[PATCH v3 5/5] git-checkout.txt: better docs for '--patch'","fromName":"Valentin Haenel","fromEmail":"valentin.haenel@gmx.de","sentAt":"2011-05-05T18:48:48Z","receivedAt":"2011-05-05T18:48:48Z","isPatch":true,"sender":{"key":"valentin.haenel@gmx.de","avatar":"https://avatars.githubusercontent.com/u/41563?v=4"},"body":"* Include '-p' in synopsis and options\n* Include a link to the git-add manpage for a description of the patch-mode.\n\nSigned-off-by: Valentin Haenel <valentin.haenel@gmx.de>\nHelped-by: Jeff King <peff@peff.net>\nMentored-by: Junio C Hamano <gitster@pobox.com>\n---\n Documentation/git-checkout.txt |    7 ++++---\n 1 files changed, 4 insertions(+), 3 deletions(-)\n\ndiff --git a/Documentation/git-checkout.txt b/Documentation/git-checkout.txt\nindex 1063f69..9d53582 100644\n--- a/Documentation/git-checkout.txt\n+++ b/Documentation/git-checkout.txt\n@@ -12,7 +12,7 @@ SYNOPSIS\n 'git checkout' [-q] [-f] [-m] [--detach] [<commit>]\n 'git checkout' [-q] [-f] [-m] [[-b|-B|--orphan] <new_branch>] [<start_point>]\n 'git checkout' [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] [--] <paths>...\n-'git checkout' --patch [<tree-ish>] [--] [<paths>...]\n+'git checkout' -p|--patch [<tree-ish>] [--] [<paths>...]\n \n DESCRIPTION\n -----------\n@@ -45,7 +45,7 @@ $ git checkout <branch>\n that is to say, the branch is not reset/created unless \"git checkout\" is\n successful.\n \n-'git checkout' [--patch] [<tree-ish>] [--] <pathspec>...::\n+'git checkout' [-p|--patch] [<tree-ish>] [--] <pathspec>...::\n \n \tWhen <paths> or `--patch` are given, 'git checkout' does *not*\n \tswitch branches.  It updates the named paths in the working tree\n@@ -183,7 +183,8 @@ the conflicted merge in the specified paths.\n \tworking tree (and if a <tree-ish> was specified, the index).\n +\n This means that you can use `git checkout -p` to selectively discard\n-edits from your current working tree.\n+edits from your current working tree. See the ``Interactive Mode''\n+section of linkgit:git-add[1] to learn how to operate the `\\--patch` mode.\n \n <branch>::\n \tBranch to checkout; if it refers to a branch (i.e., a name that,\n-- \n1.7.1\n"},{"id":"167161","messageId":"7vbozh6jrj.fsf@alter.siamese.dyndns.org","threadId":"27229","inReplyTo":"1304621271-17107-1-git-send-email-valentin.haenel@gmx.de","subject":"Re: [PATCH v3 0/5] better document 'interactive.singlekey' and '--patch'","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2011-05-05T19:16:00Z","receivedAt":"2011-05-05T19:16:00Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Valentin Haenel <valentin.haenel@gmx.de> writes:\n\n> Note that the first patch is already included in pu (93556471), but I\n> included it here again since its part of the series. Is that the right\n> thing to do, or could I have dropped it?\n\nTo me it does not make much of a difference either way.\n\nI usually try to apply a rerolled series at the same fork point as the\nprevious round, and discard the earlier ones after verifying if they are\nidentical between the two rounds (both trees and log message wording).  It\nbecomes irritating when the changes I find in this process only reverts\nwhat I fixed-up when I queued the previous round, but on the other hand,\na complete re-send will give the patch a new chance to be reviewed by\ndifferent people, so...\n"},{"id":"167162","messageId":"7v7ha56jh4.fsf@alter.siamese.dyndns.org","threadId":"27229","inReplyTo":"1304621328-17184-3-git-send-email-valentin.haenel@gmx.de","subject":"Re: [PATCH v3 3/5] git-reset.txt: better docs for '--patch'","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2011-05-05T19:22:15Z","receivedAt":"2011-05-05T19:22:15Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Valentin Haenel <valentin.haenel@gmx.de> writes:\n\n> * Include '-p' in the synopsis.\n> * Include a better wording for what 'git reset -p' does.\n>   (interactively unstage hunks)\n> * Include a link to the git-add manpage for a description of the patch-mode.\n\nYuck (just a style).\n\n> Signed-off-by: Valentin Haenel <valentin.haenel@gmx.de>\n> Helped-by: Jeff King <peff@peff.net>\n> Mentored-by: Junio C Hamano <gitster@pobox.com>\n> ---\n>  Documentation/git-reset.txt |    7 ++++---\n>  1 files changed, 4 insertions(+), 3 deletions(-)\n>\n> diff --git a/Documentation/git-reset.txt b/Documentation/git-reset.txt\n> index 8481f9d..b6ed0c7 100644\n> --- a/Documentation/git-reset.txt\n> +++ b/Documentation/git-reset.txt\n> @@ -9,7 +9,7 @@ SYNOPSIS\n>  --------\n>  [verse]\n>  'git reset' [-q] [<commit>] [--] <paths>...\n> -'git reset' --patch [<commit>] [--] [<paths>...]\n> +'git reset' --patch|-p [<commit>] [--] [<paths>...]\n\nWe don't say [--quiet|-q], so I am not sure if we care.  If we do, these\nalternative spellings of the same thing should be marked as alternatives.\n\n> @@ -39,8 +39,9 @@ working tree in one go.\n>  \tand <commit> (defaults to HEAD).  The chosen hunks are applied\n>  \tin reverse to the index.\n>  +\n> -This means that `git reset -p` is the opposite of `git add -p` (see\n> -linkgit:git-add[1]).\n> +This means that `git reset -p` is the opposite of `git add -p`, i.e.\n> +you can use it to selectively unstage hunks. See the ``Interactive Mode''\n> +section of linkgit:git-add[1] to learn how to operate the `\\--patch` mode.\n\nI would rather say \"selectively reset hunks\".  The reader should not have\nto learn an alternative terminology to understand what it does, and in\nthis particular sentence, \"reset a hunk\" is just as understandable and\ncorrect.  After all, you are resetting some hunks but not others to the\noriginal state specified by the <commit>.  If <commit> happens to be HEAD,\nthat may be equivalent to \"unstage\", but otherwise it is not even a\ncorrect description.\n"},{"id":"167165","messageId":"7v39kt6j4i.fsf@alter.siamese.dyndns.org","threadId":"27229","inReplyTo":"1304621328-17184-5-git-send-email-valentin.haenel@gmx.de","subject":"Re: [PATCH v3 5/5] git-checkout.txt: better docs for '--patch'","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2011-05-05T19:29:49Z","receivedAt":"2011-05-05T19:29:49Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Valentin Haenel <valentin.haenel@gmx.de> writes:\n\n> * Include '-p' in synopsis and options\n> * Include a link to the git-add manpage for a description of the patch-mode.\n>\n> Signed-off-by: Valentin Haenel <valentin.haenel@gmx.de>\n> Helped-by: Jeff King <peff@peff.net>\n> Mentored-by: Junio C Hamano <gitster@pobox.com>\n> ---\n\nThe order of the sign-off chain is not right (I've fixed them up so this\nis not a reason for resending).  After getting somebody's help, the final\nversion was made by you, so listing them this way\n\n    Helped-by: Jeff King <peff@peff.net>\n    Mentored-by: Junio C Hamano <gitster@pobox.com>\n    Signed-off-by: Valentin Haenel <valentin.haenel@gmx.de>\n\nwould reflect the order of events better.\n\nFYI, this patch has become like this:\n\n    Author: Valentin Haenel <valentin.haenel@gmx.de>\n    Date:   Thu May 5 20:48:48 2011 +0200\n\n    git-checkout.txt: better docs for '--patch'\n    \n    Describe '-p' as a short form of '--patch' in synopsis and options.  Also\n    refer the reader to the patch mode description of git-add documentation.\n    \n    Helped-by: Jeff King <peff@peff.net>\n    Mentored-by: Junio C Hamano <gitster@pobox.com>\n    Signed-off-by: Valentin Haenel <valentin.haenel@gmx.de>\n    Signed-off-by: Junio C Hamano <gitster@pobox.com>\n\nWill queue 1, 2, 4, and 5 with similar fix-ups.\n\nThanks.\n"},{"id":"167167","messageId":"20110505194124.GA18107@kudu.in-berlin.de","threadId":"27229","inReplyTo":"7v7ha56jh4.fsf@alter.siamese.dyndns.org","subject":"Re: [PATCH v3 3/5] git-reset.txt: better docs for '--patch'","fromName":"Valentin Haenel","fromEmail":"valentin.haenel@gmx.de","sentAt":"2011-05-05T19:41:24Z","receivedAt":"2011-05-05T19:41:24Z","isPatch":true,"sender":{"key":"valentin.haenel@gmx.de","avatar":"https://avatars.githubusercontent.com/u/41563?v=4"},"body":"* Junio C Hamano <gitster@pobox.com> [110505]:\n> Valentin Haenel <valentin.haenel@gmx.de> writes:\n> \n> > * Include '-p' in the synopsis.\n> > * Include a better wording for what 'git reset -p' does.\n> >   (interactively unstage hunks)\n> > * Include a link to the git-add manpage for a description of the patch-mode.\n> \n> Yuck (just a style).\n\nDon't like the bullets? Full sentences are preferable, eh? :)\n\n> \n> > Signed-off-by: Valentin Haenel <valentin.haenel@gmx.de>\n> > Helped-by: Jeff King <peff@peff.net>\n> > Mentored-by: Junio C Hamano <gitster@pobox.com>\n> > ---\n> >  Documentation/git-reset.txt |    7 ++++---\n> >  1 files changed, 4 insertions(+), 3 deletions(-)\n> >\n> > diff --git a/Documentation/git-reset.txt b/Documentation/git-reset.txt\n> > index 8481f9d..b6ed0c7 100644\n> > --- a/Documentation/git-reset.txt\n> > +++ b/Documentation/git-reset.txt\n> > @@ -9,7 +9,7 @@ SYNOPSIS\n> >  --------\n> >  [verse]\n> >  'git reset' [-q] [<commit>] [--] <paths>...\n> > -'git reset' --patch [<commit>] [--] [<paths>...]\n> > +'git reset' --patch|-p [<commit>] [--] [<paths>...]\n> \n> We don't say [--quiet|-q], so I am not sure if we care.  If we do, these\n> alternative spellings of the same thing should be marked as alternatives.\n\nI see, git-add and git-stash have them, git-checkout and git-reset\ndon't...\n\n> > @@ -39,8 +39,9 @@ working tree in one go.\n> >  \tand <commit> (defaults to HEAD).  The chosen hunks are applied\n> >  \tin reverse to the index.\n> >  +\n> > -This means that `git reset -p` is the opposite of `git add -p` (see\n> > -linkgit:git-add[1]).\n> > +This means that `git reset -p` is the opposite of `git add -p`, i.e.\n> > +you can use it to selectively unstage hunks. See the ``Interactive Mode''\n> > +section of linkgit:git-add[1] to learn how to operate the `\\--patch` mode.\n> \n> I would rather say \"selectively reset hunks\".  The reader should not have\n> to learn an alternative terminology to understand what it does, and in\n> this particular sentence, \"reset a hunk\" is just as understandable and\n> correct.  After all, you are resetting some hunks but not others to the\n> original state specified by the <commit>.  If <commit> happens to be HEAD,\n> that may be equivalent to \"unstage\", but otherwise it is not even a\n> correct description.\n\nWill fix and resend.\n\nV-\n"},{"id":"167172","messageId":"1304625498-23475-1-git-send-email-valentin.haenel@gmx.de","threadId":"27229","inReplyTo":"7v7ha56jh4.fsf@alter.siamese.dyndns.org","subject":"[PATCH v4 3/5] git-reset.txt: better docs for '--patch'","fromName":"Valentin Haenel","fromEmail":"valentin.haenel@gmx.de","sentAt":"2011-05-05T19:58:18Z","receivedAt":"2011-05-05T19:58:18Z","isPatch":true,"sender":{"key":"valentin.haenel@gmx.de","avatar":"https://avatars.githubusercontent.com/u/41563?v=4"},"body":"Describe '-p' as a short form of '--patch' in synopsis. Also include a better\nexplanation of this option and additionally refer the reader to the patch mode\ndescription of git-add documentation.\n\nHelped-by: Jeff King <peff@peff.net>\nMentored-by: Junio C Hamano <gitster@pobox.com>\nSigned-off-by: Valentin Haenel <valentin.haenel@gmx.de>\n---\n\nReworded the option description, turned the bullet points in the commit-message\ninto proper sentences, and fixed the sign-off-chain. Sending only patch 3/5 of\nv4 since the others have already been queued.\n\n Documentation/git-reset.txt |    7 ++++---\n 1 files changed, 4 insertions(+), 3 deletions(-)\n\ndiff --git a/Documentation/git-reset.txt b/Documentation/git-reset.txt\nindex 8481f9d..82001f2 100644\n--- a/Documentation/git-reset.txt\n+++ b/Documentation/git-reset.txt\n@@ -9,7 +9,7 @@ SYNOPSIS\n --------\n [verse]\n 'git reset' [-q] [<commit>] [--] <paths>...\n-'git reset' --patch [<commit>] [--] [<paths>...]\n+'git reset' --patch|-p [<commit>] [--] [<paths>...]\n 'git reset' [--soft | --mixed | --hard | --merge | --keep] [-q] [<commit>]\n \n DESCRIPTION\n@@ -39,8 +39,9 @@ working tree in one go.\n \tand <commit> (defaults to HEAD).  The chosen hunks are applied\n \tin reverse to the index.\n +\n-This means that `git reset -p` is the opposite of `git add -p` (see\n-linkgit:git-add[1]).\n+This means that `git reset -p` is the opposite of `git add -p`, i.e.\n+you can use it to selectively reset hunks. See the ``Interactive Mode''\n+section of linkgit:git-add[1] to learn how to operate the `\\--patch` mode.\n \n 'git reset' [--<mode>] [<commit>]::\n \tThis form resets the current branch head to <commit> and\n-- \n1.7.1\n"}]}