From: Matthias Lederhofer <matled@gmx.net>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] new environment variable GIT_TEMPLATE_DIR to override default template
Date: Sun, 28 May 2006 20:15:09 +0200 [thread overview]
Message-ID: <E1FkPnB-0005yW-UY@moooo.ath.cx> (raw)
In-Reply-To: <7v4pzadpfr.fsf@assigned-by-dhcp.cox.net>
> I like the part to let git-clone pass --template down to git-init-db,
> but once it is in place I doubt you would still need GIT_TEMPLATE_DIR.
> I'd rather not to introduce new environment variables if we can
> avoid them.
I like the variable because it makes it very easy to change the
default template directory (so I don't have to remember passing
--template every time I clone or create a new repository). But
aliases/default options (~/.git/config thread) this would make this
possible too.
> Here, $template is either empty string "", or "--template=dir"
> after argument parsing. But then it does this:
>
> > @@ -203,7 +206,7 @@ trap 'err=$?; cd ..; rm -r "$D"; exit $e
> > case "$bare" in
> > yes) GIT_DIR="$D" ;;
> > *) GIT_DIR="$D/.git" ;;
> > -esac && export GIT_DIR && git-init-db || usage
> > +esac && export GIT_DIR && git-init-db "$template" || usage
>
> which I suspect would make git-init-db barf if you did not pass
> any --template=foo option to git-clone. Did you test your patch?
Sorry, I did not run make test and did not test it without the option.
Shall I send a new patch?
prev parent reply other threads:[~2006-05-28 18:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-27 13:25 [PATCH 2/2] make init-db use GIT_TEMPLATE_DIR if --template option is not specified Petr Baudis
2006-05-27 18:57 ` [PATCH] new environment variable GIT_TEMPLATE_DIR to override default template Matthias Lederhofer
2006-05-28 17:33 ` Junio C Hamano
2006-05-28 18:15 ` Matthias Lederhofer [this message]
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=E1FkPnB-0005yW-UY@moooo.ath.cx \
--to=matled@gmx.net \
--cc=git@vger.kernel.org \
--cc=junkio@cox.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).