From: "Jakub Narębski" <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: [RFD] Place to document magic pathspecs like ":/" and pathspec handling
Date: Wed, 29 Jun 2016 21:47:59 +0200 [thread overview]
Message-ID: <577425EF.6030900@gmail.com> (raw)
Hello,
123456789012345678901234567890123456789012345678901234567890123456789012345|
I have noticed that the magic pathspec ":/" is described only in RelNotes
for revision 1.7.6:
|* A magic pathspec ":/" tells a command that limits its operation to the current directory when ran from a subdirectory to work on the entire working tree. In general, ":/path/to/file" would be relative to the root of the working tree hierarchy. After "git reset --hard; edit Makefile; cd t/", "git add -u" would be a no-op, but "git add -u :/" would add the updated contents of the Makefile at the top level. If you want to name a path in the current subdirectory whose unusual name begins with ":/", you can name it by "./:/that/path" or by "\:/that/path".|
||
|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
it would be better to create a separate manpage for issues related
to pathspec handling (of which ":/" is only one part)... but then
what should it be named?
What do you think?
--
Jakub Narębski
|||
next reply other threads:[~2016-06-29 19:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-29 19:47 Jakub Narębski [this message]
2016-06-29 19:51 ` [RFD] Place to document magic pathspecs like ":/" and pathspec handling Junio C Hamano
2016-06-29 21:22 ` Jakub Narębski
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=577425EF.6030900@gmail.com \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
/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).