list mirror (unofficial, one of many)
 help / color / Atom feed
From: "Robert P. J. Day" <>
To: Junio C Hamano <>
Cc: Kevin Daudt <>, Git Mailing list <>
Subject: Re: "man git-checkout", man page is inconsistent between SYNOPSIS and details
Date: Sun, 1 Oct 2017 06:05:44 -0400 (EDT)
Message-ID: <alpine.LFD.2.21.1710010603340.17338@localhost.localdomain> (raw)
In-Reply-To: <>

On Sun, 1 Oct 2017, Junio C Hamano wrote:

> "Robert P. J. Day" <> writes:
> >   it's simply a matter of the forms not matching between the SYNOPSIS
> > and the DESCRIPTION sections. am i making sense?
> I think the whole thing is wrong and the root cause is because the
> (relatively newer) description of the "--patch" mode lazily tried to
> piggy-back the description of existing "check out from the index or
> tree-ish" mode, ending up in a confusing description...

  ... big snip ...

ok, i'm going to have to digest all that; pretty sure someone else
will need to change the man page to clarify the apparent inconsistency
i was referring to:

       git checkout [-p|--patch] [<tree-ish>] [--] [<paths>...]
       git checkout [-p|--patch] [<tree-ish>] [--] <pathspec>...

and on that note, i'll get back to proofreading.



Robert P. J. Day                                 Ottawa, Ontario, CANADA


  reply index

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-30  9:27 Robert P. J. Day
2017-09-30 14:32 ` Kevin Daudt
2017-09-30 15:01   ` Robert P. J. Day
2017-09-30 22:04   ` Robert P. J. Day
2017-10-01  3:49     ` Junio C Hamano
2017-10-01 10:05       ` Robert P. J. Day [this message]
2017-10-02  0:29         ` Junio C Hamano
2017-10-11  2:39           ` [PATCH] checkout doc: clarify command line args for "checkout paths" mode Junio C Hamano
2017-10-11  3:22             ` Jonathan Nieder
2017-10-11  5:02               ` Junio C Hamano
2017-10-11  5:16                 ` Jonathan Nieder

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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.LFD.2.21.1710010603340.17338@localhost.localdomain \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link list mirror (unofficial, one of many)

Archives are clonable:
	git clone --mirror
	git clone --mirror http://ou63pmih66umazou.onion/git
	git clone --mirror http://czquwvybam4bgbro.onion/git
	git clone --mirror http://hjrcffqmbrq6wope.onion/git

Example config snippet for mirrors

Newsgroups are available over NNTP:

 note: .onion URLs require Tor:

AGPL code for this site: git clone