From: "Jakub Narębski" <jnareb@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: [RFD] Place to document magic pathspecs like ":/" and pathspec handling
Date: Wed, 29 Jun 2016 23:22:03 +0200 [thread overview]
Message-ID: <57743BFB.9040709@gmail.com> (raw)
In-Reply-To: <CAPc5daVqjhWrJjNX6monHdMTRwimbjz==j9B2FS-nXNCqPDCYQ@mail.gmail.com>
W dniu 2016-06-29 o 21:51, Junio C Hamano pisze:
> On Wed, Jun 29, 2016 at 12:47 PM, Jakub Narębski <jnareb@gmail.com> wrote:
>> I have noticed that the magic pathspec ":/" is described only in RelNotes
>> for revision 1.7.6:
>> |I think the reason might be that there was no good place to put that
>> information in. Nowadays we have gitcli(7) manual page, but perhaps
> $ git help glossary
>
> look for pathspec.
Thanks. I haven't noticed that.
But I think it is not the best place to keep this documentation.
There are the following issues with it:
* it is hard to find; I did not search _glossary_ for information
about how Git handles pathspecs, I would search it if I didn't know
what pathspec means.
* it is longest entry in glossary, and the only one with nested
list, but
* it is also too short to describe how Git handles pathspecs in detail,
and a bit cryptic; there are no examples (so grepping docs for '":/"'
didn't found it).
--
Jakub Narębski
next prev parent reply other threads:[~2016-06-29 21:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-29 19:47 [RFD] Place to document magic pathspecs like ":/" and pathspec handling Jakub Narębski
2016-06-29 19:51 ` Junio C Hamano
2016-06-29 21:22 ` Jakub Narębski [this message]
2016-06-29 21:28 ` Junio C Hamano
2016-06-30 9:42 ` Jakub Narębski
2016-06-30 15:14 ` Duy Nguyen
2016-07-01 6:42 ` Jeff King
2016-07-01 13:17 ` Jakub Narębski
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=57743BFB.9040709@gmail.com \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).