Git development
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Git Mailing list <git@vger.kernel.org>
Subject: "man gitattributes" doesn't explain comma-separated attribute values
Date: Sat, 16 Mar 2019 08:22:24 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.2.21.1903160816410.10724@localhost.localdomain> (raw)


  more nitpicking, but i'm working my way through the intricacies of
attributes and putting together some (allegedly) simple examples for a
class i'm giving on monday, and i noted a couple possible shortcomings
in "man gitattributes".

  as a working example, i looked at the top-level .gitattributes file
in the git source code itself, which opens with:

  * whitespace=!indent,trail,space
  *.[ch] whitespace=indent,trail,space diff=cpp
  *.sh whitespace=indent,trail,space eol=lf
  ... snip ...

first observation is that i see nothing in the man page that explains
the notion of a comma-separated list of attribute values. maybe i
missed it or maybe it's supposed to be intuitively obvious, but
there's nothing i can see that mentions the possibility.

  related to that is that there is no explanation as to how to
interpret:

  * whitespace=!indent,trail,space

does the "!" apply to "indent" or to the entire list? the man page
doesn't say.

  just being pedantic again.

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                  http://crashcourse.ca/dokuwiki

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================

             reply	other threads:[~2019-03-16 12:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-16 12:22 Robert P. J. Day [this message]
2019-03-16 13:13 ` "man gitattributes" doesn't explain comma-separated attribute values Ævar Arnfjörð Bjarmason
2019-03-16 13:48   ` Robert P. J. Day
2019-03-16 21:58 ` Johannes Sixt
2019-03-16 22:09   ` Robert P. J. Day
2019-03-17  8:18     ` Johannes Sixt
2019-03-18 10:10       ` Philip Oakley

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=alpine.LFD.2.21.1903160816410.10724@localhost.localdomain \
    --to=rpjday@crashcourse.ca \
    --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