Re: [PATCH] Quick description of possible gitattributes system

[Andy Parkins <andyparkins@gmail.com>]

On Friday 2007, March 02, Brian Gernhardt wrote:

> I'm sorry, I was assuming that information on what to do with each
> attribute would be in the config file while a majority of the
> attribute information was in an in-tree file.  I was actually
> assuming:

It's definitely in the .gitattributes file, but is also optionally in 
the config as well.  This means that a user can always override 
something locally - i.e. they're always in control of their own 
repository, even when they disagree with upstream (perhaps).

> .git/config:
> [attribute "image"]
>     show = ...
>     merge = ...
>
> With the ability to have additional "path =" entries for *local*
> overrides/additions.  Storing the handler information in

That's almost exactly it; but it makes the assumption that each 
attribute will have one unique handler.  Separating them means that 
multiple attributes can use one handler (or set of handlers).

> the .gitattributes is one of the worst things you could do, IMHO.  It
> assumes that people will have a homogenous environment to develop in,

Oh definitely.  This is one thing that everybody absolutely agrees on.  
The in-tree file /only/ adds attributes and never says what effect 
those attributes have.



Andy

-- 
Dr Andy Parkins, M Eng (hons), MIET
andyparkins@gmail.com