git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] checkout doc: clarify command line args for "checkout paths" mode

From
Jonathan Nieder <jrnieder@gmail.com>
Date
Oct 11, 2017, 05:16 UTC
Message-ID
<20171011051604.GA140836@aiede.mtv.corp.google.com>
In-Reply-To
<xmqqzi8ymg4f.fsf@gitster.mtv.corp.google.com>
Junio C Hamano wrote:
> here is another attempt, this time to avoid "Restore" and <paths>...
>
>  Documentation/git-checkout.txt | 30 ++++++++++++++++--------------
>  1 file changed, 16 insertions(+), 14 deletions(-)
Thanks.  I find this one easier to read indeed.
[...]
> --- a/Documentation/git-checkout.txt
> +++ b/Documentation/git-checkout.txt
> @@ -13,7 +13,8 @@ SYNOPSIS
[...]
Show 10 quoted lines
> @@ -101,6 +95,14 @@ specific side of the merge can be checked out of the index by
>  using `--ours` or `--theirs`.  With `-m`, changes made to the working tree
>  file can be discarded to re-create the original conflicted merge result.
>  
> +'git checkout' (-p|--patch) [<tree-ish>] [--] [<pathspec>...]::
> +	This is similar to the "check out paths to the working tree
> +	from either the index or from a tree-ish" mode described
> +	above, but lets you use the interactive interface to show
> +	the "diff" output and choose which hunks to use in the
> +	result.  See below for the descriptoin of `--patch` option.
nit: s/descriptoin/description/
With that tweak,
Reviewed-by: Jonathan Nieder <jrnieder@gmail.com>
Thanks.
Previous: Junio C Hamano
Message 11 of 11 in “"man git-checkout", man page is inconsistent between SYNOPSIS and details”
  1. Robert P. J. DaySep 30, 2017
  2. Kevin DaudtSep 30, 2017
  3. Robert P. J. DaySep 30, 2017
  4. Robert P. J. DaySep 30, 2017
  5. Junio C HamanoOct 1, 2017
  6. Robert P. J. DayOct 1, 2017
  7. Junio C HamanoOct 2, 2017
  8. checkout doc: clarify command line args for "checkout paths" modeJunio C Hamano, Oct 11, 2017
  9. Jonathan NiederOct 11, 2017
  10. Junio C HamanoOct 11, 2017
  11. Jonathan NiederOct 11, 2017

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.