From: Jeff King <peff@peff.net>
Date: Mon, 31 Mar 2008 02:47:55 GMT
Subject: Re: [BUG?] git-archive ignores remote .gitattributes (was: .git/info/attributes not cloned)
Message-ID: <20080331024755.GA690@coredump.intra.peff.net>
In-Reply-To: <alpine.LSU.1.00.0803281321260.18259@racer.site>

On Fri, Mar 28, 2008 at 01:22:53PM +0100, Johannes Schindelin wrote:

> > "git-archive --remote=/some/repo" will ignore /some/repo/.gitattributes, 
> > but check /some/repo/info/attributes.
> > 
> > I think the problem is in the loop that looks for .gitattributes, which 
> > seems to do so by taking the current path and iterating down through it?
> 
> The problem is that "git archive --remote" operates on the remote 
> repository as if it were bare.  Which in many cases is true.
> 
> So I'd submit that this is not the usage .gitattributes is meant for, and 
> that you should clone the thing if you want to generate archives heeding 
> the .gitattributes.

I don't think it makes sense to operate on or take input from the
working tree of a remote; no other other command does, I don't think. I
had assumed, though, that .gitattributes files _in the tree being
exported_ would be used.

I thought there was some discussion of that a while ago (or possibly of
looking up .gitignore in the same way).

-Peff