On Sat, Jul 2, 2011 at 9:57 PM, Jeff King <peff@xxxxxxxx> wrote:
> You could try setting "$ENV{GIT_TRACE} = 1", which will dump all of the
> git commands being called to stderr (and presumaby your log). That would
> double-check that the option is being passed.
Great. Thanks for the tip.
> I think what might be happening, though, is that git does not do a good
> job checking .gitattributes files inside trees; it only checks the
> .gitattributes in the working tree, even if you are diffing a tree. But
> in the case of a bare repository, we don't even have a working tree at
> all.
>
> You can try working around it like this:
>
> cd /path/to/bare/repo.git
> git show HEAD:.gitattributes >info/attributes
This did not work, for what I think might be an obvious reason; I do
not have a .gitattributes file *in* the repo or any repos anymore, but
a global one. See below.
[dreamhost-server]$ git show HEAD:.gitattributes >info/attributes
fatal: Path '.gitattributes' exists on disk, but not in 'HEAD'.
> which will make the repository-wide non-version-controlled gitattributes
> the same as the last committed version. The problem is that it won't be
> automatically updated as you commit and push changes to .gitattributes.
I thought my plan was to try and avoid this by using the
core.attributesfile directive, forcing this stuff to operate system
(well, account, besides the point here) wide on all repos with
specifying a .gitattributes (or, since it base bare, as you pointed
out yourself, $GIT_REPO_DIR/info/attributes) every single time. Did I
misunderstand the mailing list thread that mentioned this a while
back?
[dreamhost-server]$ git config --list --global
diff.odf.textconv=odt2txt
diff.odf.binary=false
diff.pdf.textconv=pdftotext
diff.pdf.binary=false
core.attributesfile=~/.gitattributes
Inside one of the troublesome repos (so resultant collection of global
and repo-specific config):
[dreamhost-server]$ git config --list
diff.odf.textconv=odt2txt
diff.odf.binary=false
diff.pdf.textconv=pdftotext
diff.pdf.binary=false
core.attributesfile=~/.gitattributes
core.repositoryformatversion=0
core.filemode=true
core.bare=true
gitweb.owner=alharaka@xxxxxxxxx
diff.odf.textconv=odt2txt
This is the reason I went through the trouble of compiling an updated
version in my account (as opposed to the installed version on the
Dreamhost box; they are stuck at version 1.7.1.1; I saw this mentioned
on a thread somewhere and wanted to get the "latest" (well latest
stable version) to avoid this kind of problem? Was that the right
thing to do? Will it even work in this case? I get the feeling from
your response I was expecting a lot with RTFM'ing more. I have a
script, as described in the Github HOWTO, that creates the bare repo
as desired for me. So, if this will not work, I will just modify my
version of the bash script to handle this. I just am obviously not
sure what the "proper" approach or best practice is anymore.
Thanks again for your help. I really appreciate it. I am new to git,
but LOVE what you guys have being doing. I never used any DRCS before
this, personally or professionally, but read snippets of howtos and so
much good press I decided it was time I mooch off you guys to organize
my life. :-)
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html