From: Andy Parkins <andyparkins@gmail.com>
To: git@vger.kernel.org
Cc: Junio C Hamano <junkio@cox.net>
Subject: Re: [PATCH 1/3] Add basic infrastructure to assign attributes to paths
Date: Fri, 13 Apr 2007 10:33:12 +0100 [thread overview]
Message-ID: <200704131033.15751.andyparkins@gmail.com> (raw)
In-Reply-To: <7vr6qod4wh.fsf@assigned-by-dhcp.cox.net>
On Friday 2007, April 13, Junio C Hamano wrote:
> parent directories. Lines in $GIT_DIR/info/attributes file are
> used as the lowest precedence default rules.
Shouldn't this be the highest precedence? This would be important for
those cases where I (as a fringe developer) disagree with an attribute
that's been assigned in-tree. I don't want to force my will on every
other developer, but would want my repository to work how I like it.
For example: what if I /can/ read postscript :-)
Incidentally - already I love gitattributes - nicely done Junio.
Andy
--
Dr Andy Parkins, M Eng (hons), MIET
andyparkins@gmail.com
next prev parent reply other threads:[~2007-04-13 9:33 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-13 9:01 [PATCH 1/3] Add basic infrastructure to assign attributes to paths Junio C Hamano
2007-04-13 9:33 ` Andy Parkins [this message]
2007-04-15 0:59 ` Junio C Hamano
2007-04-15 1:01 ` [PATCH 1/2] attribute macro support Junio C Hamano
2007-04-15 1:03 ` [PATCH 2/2] Define a few built-in attribute rules Junio C Hamano
2007-04-15 1:41 ` Linus Torvalds
2007-04-15 1:48 ` Brian Gernhardt
2007-04-15 2:04 ` Junio C Hamano
2007-04-15 2:34 ` Junio C Hamano
2007-04-15 16:21 ` Johannes Schindelin
2007-04-15 19:58 ` Junio C Hamano
2007-04-15 4:30 ` Linus Torvalds
2007-04-15 23:10 ` [PATCH] Fix 'crlf' attribute semantics Junio C Hamano
2007-04-15 23:12 ` [PATCH] Fix 'diff' " Junio C Hamano
2007-04-15 23:37 ` [PATCH] Fix 'crlf' " Tom Prince
2007-04-15 23:44 ` Junio C Hamano
2007-04-16 6:21 ` Raimund Bauer
2007-04-13 15:04 ` [PATCH 1/3] Add basic infrastructure to assign attributes to paths Linus Torvalds
2007-04-15 15:54 ` Johannes Schindelin
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=200704131033.15751.andyparkins@gmail.com \
--to=andyparkins@gmail.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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).