Re: `git check-attr' problems & questions

> Hi,
> 
> [quoted text reordered for convenience]
> 
> Eli Barzilay wrote:
> 
> > I'm trying to use .gitattributes to use some custom properties that we
> > have in an svn repository which is migrating to git,
> [...]
> > So my first question is -- am I missing something obvious?  It almost
> > looks like `check-attr' is intended only for low-level use...
> 
> Yep.  It’s listed under “purehelpers” (Internal helper commands) in
> command-list.txt and hence git(1).

> I suspect a good place to put a user-visible equivalent would be a
> future ‘git ls’ command [1].
> 
> Therefore...
> 
> > Fixing the first problem seems like it would be easy with a quick
> > shell script (maybe even with just an alias),
> 
> If it proves pleasant to use, it would be very nice if you could
> send a copy of such a shell script after a while.  Experiments like
> this are the foundation of a good UI.

> > 2. I'm also trying to use an attribute on a hook script on the server
> >    (with the idea that email notifications are sent according to the
> >    set of modified files) -- but it looks like `git check-attr'
> >    doesn't work on a bare repository.
> 
> Current ‘git check-attr’ reads its attributes from actual .gitattribute
> files in the work tree first and then examines the versions registered
> in the index.  So the secret is to read the .gitattribute files you care
> about into a temporary index file --- e.g., something like this.
> 
>  : "Usage: $0 commit check-attr-args" &&
> 
>  GIT_INDEX=tmp-index git read-tree --reset -i "$1" &&
>  shift &&
>  GIT_INDEX=tmp-index git check-attr "$@" &&
>  rm tmp-index