From: "David Kågedal" <davidk@lysator.liu.se>
To: git@vger.kernel.org
Subject: Re: [PATCH] Added -d and -e options to the "git" script.
Date: Mon, 19 Sep 2005 16:24:10 +0200 [thread overview]
Message-ID: <u5tvf0xb0fp.fsf@lysator.liu.se> (raw)
In-Reply-To: 432EC7D6.6080105@gmail.com
A Large Angry SCM <gitzilla@gmail.com> writes:
> David Kågedal wrote:
>> These flags override the GIT_DIR and EDITOR environment variables.
>>
> [Patch snipped]
>
> An option for GIT_DIR maybe since it's a Git environment variable but a
> command line option to change the EDITOR _environment_ variable is NOT
> appropriate for git.
Yeah, I should have separated those two so that the GIT_DIR option
could be accepted on its own. And it should maybe have a --git-dir=
log form as well.
The reason I did -e too was simply that I needed it for the same
reason I needed -d. I wanted to run git with specific values for
GIT_DIR and EDITOR without having to setenv them in emacs. But the
EDITOR trick I'm using is a hack and should be replaced anyway. (I use
EDITOR=cat to get access to the default commit message with comments
from 'git commit').
So please disregard the -e part of my patch for now. You are free to
disregard the -d part as well, but I think that makes some kind of
sense.
And If we go down this path, maybe flags for other GIT_* environment
variables should be settable with git command line flags too?
--
David Kågedal
next prev parent reply other threads:[~2005-09-19 14:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-18 18:18 Add "--git-dir" flag to git-rev-parse Linus Torvalds
2005-09-19 10:19 ` [PATCH] Added -d and -e options to the "git" script David Kågedal
2005-09-19 14:14 ` A Large Angry SCM
2005-09-19 14:24 ` David Kågedal [this message]
2005-09-19 14:42 ` A Large Angry SCM
2005-09-19 15:08 ` David Kågedal
2005-09-19 14:42 ` Matthias Urlichs
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=u5tvf0xb0fp.fsf@lysator.liu.se \
--to=davidk@lysator.liu.se \
--cc=git@vger.kernel.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).