From: Stefan Beller <sbeller@google.com>
To: unlisted-recipients:; (no To-header on input)
Cc: pclouds@gmail.com, gitster@pobox.com, git@vger.kernel.org,
Jens.Lehmann@web.de, jrnieder@gmail.com,
Stefan Beller <sbeller@google.com>
Subject: [PATCHv2 0/5] pathspec labels [WAS: submodule groups]
Date: Fri, 13 May 2016 16:13:21 -0700 [thread overview]
Message-ID: <20160513231326.8994-1-sbeller@google.com> (raw)
I am happy with the results of the label experiments. (Mainly writing the tests)
>> Isn't the former be "label="
> I do not know what you mean by the latter. I would understand
>"pretend this has all the labels under the sun", though.
See the new tests what I mean. It cleared up for me as well when writing them.
> I am wondering where we should sanity check (and die, pointing out
> an error in .gitattributes file). Is this function a good place to
> reject TRUE and FALSE?
TRUE and FALSE are solved issues in this series. However we still want
funny characters not be used. What if we want to use them as
special characters in the future? (e.g. 'label*' for 'labelA' or 'labelB'
or label{A,B} for the same)
I think it is too late in the matching, so ideally we would check label
names when they are assigned (i.e. while editing the .gitattributes file)
That is not in our control, though.
And during use of match_pathspec it is already to late to die(...)
for bad labels, because the labels may not be in control for the user
(She just cloned the repository and wants to inspect certain files,
which are labeled "$*&^".) So for now we just output a warning for
these cases, in the hope that content creatos upstream respect the
recommendation for labels.
Feedback welcome!
Thanks,
Stefan
Stefan Beller (5):
Documentation: fix a typo
Documentation: correct typo in example for querying attributes
pathspec: move long magic parsing out of prefix_pathspec
pathspec: move prefix check out of the inner loop
pathspec: record labels
Documentation/gitattributes.txt | 14 ++-
Documentation/glossary-content.txt | 4 +
Documentation/technical/api-gitattributes.txt | 2 +-
dir.c | 50 ++++++++
pathspec.c | 110 +++++++++++------
pathspec.h | 1 +
t/t6134-pathspec-with-labels.sh | 164 ++++++++++++++++++++++++++
7 files changed, 305 insertions(+), 40 deletions(-)
create mode 100755 t/t6134-pathspec-with-labels.sh
--
2.8.2.401.gb7348ac.dirty
next reply other threads:[~2016-05-13 23:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-13 23:13 Stefan Beller [this message]
2016-05-13 23:13 ` [PATCH 1/5] Documentation: fix a typo Stefan Beller
2016-05-13 23:13 ` [PATCH 2/5] Documentation: correct typo in example for querying attributes Stefan Beller
2016-05-13 23:13 ` [PATCH 3/5] pathspec: move long magic parsing out of prefix_pathspec Stefan Beller
2016-05-13 23:13 ` [PATCH 4/5] pathspec: move prefix check out of the inner loop Stefan Beller
2016-05-13 23:13 ` [PATCH 5/5] pathspec: record labels Stefan Beller
2016-05-14 19:23 ` Junio C Hamano
2016-05-16 17:16 ` Stefan Beller
2016-05-16 17:38 ` Junio C Hamano
2016-05-16 17:46 ` Stefan Beller
2016-05-16 18:52 ` Junio C Hamano
2016-05-16 19:03 ` Stefan Beller
2016-05-16 19:08 ` Junio C Hamano
2016-05-16 19:12 ` Stefan Beller
2016-05-16 19:27 ` Junio C Hamano
2016-05-16 17:55 ` Stefan Beller
2016-05-16 18:43 ` Junio C Hamano
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=20160513231326.8994-1-sbeller@google.com \
--to=sbeller@google.com \
--cc=Jens.Lehmann@web.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@gmail.com \
--cc=pclouds@gmail.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).