From: Petr Baudis <pasky@ucw.cz>
To: Junio C Hamano <junkio@cox.net>
Cc: Chris Wright <chrisw@osdl.org>,
Linus Torvalds <torvalds@osdl.org>,
git@vger.kernel.org
Subject: Template files location
Date: Fri, 5 Aug 2005 11:43:24 +0200 [thread overview]
Message-ID: <20050805094324.GF29216@pasky.ji.cz> (raw)
In-Reply-To: <7vd5otov7s.fsf@assigned-by-dhcp.cox.net>
Dear diary, on Fri, Aug 05, 2005 at 06:37:11AM CEST, I got a letter
where Junio C Hamano <junkio@cox.net> told me that...
> We install files in $(HOME)/etc/git-core/templates/ directory.
>
> In the standard binary distribution scheme, it should probably
> go to either /usr/share or /etc; the former if the distribution
> prefers static boilerplate files in /usr/share, latter if we
> consider them site-specific conffiles. I just discussed this
> privately with a Debian person on the list today, and we are in
> favor of installing it under /usr/share/git-core/templates,
> because we do not expect the contents of the standard templates
> directory will not be a per-site customization [*1*].
>
> In any case, this means that the make drivers like spec.in and
> debian/rules would need to override some make variables when
> they invoke the main Makefile.
Any reason why that's not the default destination then?
Or you can try /etc/git-core/ and fall back to /usr/share/git-core :-)
--
Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
If you want the holes in your knowledge showing up try teaching
someone. -- Alan Cox
next parent reply other threads:[~2005-08-05 9:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <42DC4537.2080103@orionmulti.com>
[not found] ` <20050805024222.GE7762@shell0.pdx.osdl.net>
[not found] ` <42F2E571.6040207@orionmulti.com>
[not found] ` <7voe8dow4w.fsf@assigned-by-dhcp.cox.net>
[not found] ` <20050805042332.GG7762@shell0.pdx.osdl.net>
[not found] ` <7vd5otov7s.fsf@assigned-by-dhcp.cox.net>
2005-08-05 9:43 ` Petr Baudis [this message]
2005-08-05 17:33 ` Template files location Junio C Hamano
2005-08-05 17:50 ` A Large Angry SCM
2005-08-10 22:03 ` Matthias Urlichs
2005-08-09 20:42 ` Petr Baudis
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=20050805094324.GF29216@pasky.ji.cz \
--to=pasky@ucw.cz \
--cc=chrisw@osdl.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=torvalds@osdl.org \
/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).