git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Brandon Williams <bmwill@google.com>
To: git@vger.kernel.org
Cc: Brandon Williams <bmwill@google.com>,
	sbeller@google.com, pclouds@gmail.com
Subject: [PATCH 0/2] bringing attributes to pathspecs
Date: Thu,  9 Mar 2017 13:07:54 -0800	[thread overview]
Message-ID: <20170309210756.105566-1-bmwill@google.com> (raw)

This small series extends the pathspec magic to allow users to specify
attributes that files must have in order for a pathspec to 'match' a file.

One potential use for this is to allow a repository to specify attributes for a
set of files.  The user can then specify that attribute as a pathspec to
perform various operations only on that set of files. One simple example:

	git ls-files -- ":(attr:text)"

can be used to list all of the files with the 'text' attribute.

Brandon Williams (2):
  pathspec: allow querying for attributes
  pathspec: allow escaped query values

 Documentation/glossary-content.txt |  20 ++++
 attr.c                             |  17 ++++
 attr.h                             |   1 +
 dir.c                              |  43 ++++++++-
 pathspec.c                         | 165 ++++++++++++++++++++++++++++++--
 pathspec.h                         |  16 +++-
 t/t6135-pathspec-with-attrs.sh     | 190 +++++++++++++++++++++++++++++++++++++
 7 files changed, 442 insertions(+), 10 deletions(-)
 create mode 100755 t/t6135-pathspec-with-attrs.sh

-- 
2.12.0.246.ga2ecc84866-goog


             reply	other threads:[~2017-03-09 21:08 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-09 21:07 Brandon Williams [this message]
2017-03-09 21:07 ` [PATCH 1/2] pathspec: allow querying for attributes Brandon Williams
2017-03-09 22:19   ` Jonathan Tan
2017-03-10 18:26     ` Brandon Williams
2017-03-13  2:43   ` Junio C Hamano
2017-03-13 18:30     ` Stefan Beller
2017-03-09 21:07 ` [PATCH 2/2] pathspec: allow escaped query values Brandon Williams
2017-03-09 22:31   ` Jonathan Tan
2017-03-10 18:53     ` Brandon Williams
2017-03-09 21:22 ` [PATCH 0/2] bringing attributes to pathspecs Stefan Beller
2017-03-10 18:59 ` [PATCH v2 " Brandon Williams
2017-03-10 18:59   ` [PATCH v2 1/2] pathspec: allow querying for attributes Brandon Williams
2017-03-10 19:56     ` Jonathan Tan
2017-03-11  0:28       ` Brandon Williams
2017-03-10 18:59   ` [PATCH v2 2/2] pathspec: allow escaped query values Brandon Williams
2017-03-13 18:23   ` [PATCH v3 0/2] bringing attributes to pathspecs Brandon Williams
2017-03-13 18:23     ` [PATCH v3 1/2] pathspec: allow querying for attributes Brandon Williams
2017-03-13 18:23     ` [PATCH v3 2/2] pathspec: allow escaped query values Brandon Williams
2017-03-13 22:30     ` [PATCH v3 0/2] bringing attributes to pathspecs Junio C Hamano
2017-03-13 22:38       ` Brandon Williams
2017-03-21 10:51     ` Duy Nguyen
2017-03-21 15:51       ` Junio C Hamano
2017-03-21 16:52       ` Brandon Williams

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

  List information: http://vger.kernel.org/majordomo-info.html

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

  git send-email \
    --in-reply-to=20170309210756.105566-1-bmwill@google.com \
    --to=bmwill@google.com \
    --cc=git@vger.kernel.org \
    --cc=pclouds@gmail.com \
    --cc=sbeller@google.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).