git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Alex Riesen" <raa.lkml@gmail.com>
To: "Junio C Hamano" <gitster@pobox.com>
Cc: "Jeff King" <peff@peff.net>,
	"Maciej Pasternacki" <maciej@pasternacki.net>,
	git@vger.kernel.org
Subject: Re: [PATCH] -C/--chdir command line option
Date: Mon, 20 Oct 2008 08:26:12 +0200	[thread overview]
Message-ID: <81b0412b0810192326n7ace9d4fjd8013cbe1872df22@mail.gmail.com> (raw)
In-Reply-To: <7vhc774ydr.fsf@gitster.siamese.dyndns.org>

2008/10/20 Junio C Hamano <gitster@pobox.com>:
> Junio C Hamano <gitster@pobox.com> writes:
> I wouldn't however suggest allowing the syntax to set environment
> variables, like:
>
>        $ git GIT_AUTHOR_NAME="A U Thor" commit
>
> as this is something your shell lets you do easily, i.e:
>
>        $ GIT_AUTHOR_NAME="A U Thor" git commit
>

No, someplace else it doesn't (yes, windows again).
It is mostly hard to do there, because the system shell is so
primitive, and installation of something sane (sh or env) is
an additional (and hard to explain to windows zealots) hassle.

And even in something like Perl it is hard: you cannot
change the environment just for the child process, you
have to change your own, run the process and change
it back.

So, yes, I like your suggestion, but I'd like to _include_
setting all the Git's environment.

  reply	other threads:[~2008-10-20  6:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-19  0:02 [PATCH] -C/--chdir command line option Maciej Pasternacki
2008-10-19 13:17 ` Jeff King
2008-10-19 13:47   ` Maciej Pasternacki
2008-10-19 14:16     ` Jeff King
2008-10-19 15:24       ` Maciej Pasternacki
2008-10-20  4:55       ` Junio C Hamano
2008-10-20  5:41         ` Junio C Hamano
2008-10-20  6:26           ` Alex Riesen [this message]
2008-10-20 12:57         ` Michael J Gruber
2008-10-20 13:59   ` Nguyen Thai Ngoc Duy
     [not found] <DDFCD680-C477-4BE5-AB71-3F26048E26D1@pasternacki.net>
2008-10-20  7:28 ` Maciej Pasternacki

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=81b0412b0810192326n7ace9d4fjd8013cbe1872df22@mail.gmail.com \
    --to=raa.lkml@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=maciej@pasternacki.net \
    --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).