git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: Jeff King <peff@peff.net>
Cc: Al Haraka <alharaka@gmail.com>,
	git@vger.kernel.org, Jakub Narebski <jnareb@gmail.com>
Subject: Re: Gitweb 1.7.5 and Textconv Configuration
Date: Sat, 02 Jul 2011 13:23:38 -0700 (PDT)	[thread overview]
Message-ID: <m3aacw5t5x.fsf@localhost.localdomain> (raw)
In-Reply-To: <20110702195735.GA15542@sigill.intra.peff.net>

Jeff King <peff@peff.net> writes:
> On Sat, Jul 02, 2011 at 10:18:55PM +0300, Al Haraka wrote:
> 
> > > 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?
> 
> Ah, I see. That seems like a reasonable solution. Are you sure that the
> user running gitweb as a CGI is the same as the user you log in as? That
> is, are you sure that ~/.gitconfig is being parsed when it is called as
> a CGI, and it's not looking in ~www/.gitconfig or something?
> 
> It would depend how your hosting is set up.

Well, there is also system wide $(prefix)/etc/gitconfig file...
 
> > 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.
> 
> It sounds like it should work to me, but I've not tested it (nor do I
> even run gitweb; I just have an interest in textconv).

The question is if --textconv works with git-diff-tree, because that
is what gitweb uses.

BTW. we could use --textconv in 'blob' and 'blame' views (it is
documented that git-cat-file supports --textconv, and it is checked in
git testsuite but not documented that git-blame supports --textconv).
But it would require changes to gitweb.


Hoping that this email will made it...
-- 
Jakub Narebski
Poland
ShadeHawk on #git

  reply	other threads:[~2011-07-02 20:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-02  9:50 Gitweb 1.7.5 and Textconv Configuration Al Haraka
2011-07-02 10:43 ` Jeff King
2011-07-02 10:44   ` Jeff King
2011-07-02 11:14     ` Al Haraka
2011-07-02 18:57       ` Jeff King
2011-07-02 19:18         ` Al Haraka
2011-07-02 19:57           ` Jeff King
2011-07-02 20:23             ` Jakub Narebski [this message]
2011-07-02 21:10               ` Jeff King
2011-07-02 21:22                 ` Jakub Narebski
2011-07-02 21:10               ` Al Haraka
2011-07-06 13:59   ` Jakub Narebski
2011-07-06 15:13     ` [PATCH] docs: document --textconv diff option Jeff King

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=m3aacw5t5x.fsf@localhost.localdomain \
    --to=jnareb@gmail.com \
    --cc=alharaka@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.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).