From: Thomas Rast <trast@student.ethz.ch>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: "Nathan W. Panike" <nathan.panike@gmail.com>,
<git@vger.kernel.org>,
Peter Kjellerstedt <peter.kjellerstedt@axis.com>
Subject: Re: [PATCH RFC] Add a config verbose option fetch and push
Date: Sat, 22 May 2010 15:34:18 +0200 [thread overview]
Message-ID: <201005221534.18529.trast@student.ethz.ch> (raw)
In-Reply-To: <AANLkTimQzAM7qA32FRFvQC1cx7UEEKtBxjU89whrSqF5@mail.gmail.com>
Ævar Arnfjörð Bjarmason wrote:
> On Sat, May 22, 2010 at 10:44, Thomas Rast <trast@student.ethz.ch> wrote:
> > Ævar Arnfjörð Bjarmason wrote:
> > That would completely ruin the scriptability of almost all commands.
> > Imagine the user added the following options as default:
> > add --edit
[...]
> > I'm sure you can find one option that changes the command in something
> > completely different *for every command*.
>
> Sure. But so would adding this as git-add to your $PATH:
>
> #!/bin/sh
> /usr/lib/git-core/git-add --edit $@
Two points:
* This way is not documented in git-config(1), as the proposed
interface would have to be; hence, it is not "official".
* More importantly, it doesn't work; for builtins such as git-add, not
even if you put it under the `git --exec-path` (yes, I've tested
this).
> Git already has plenty of ways to shoot yourself in the foot.
Can't argue with that.
--
Thomas Rast
trast@{inf,student}.ethz.ch
next prev parent reply other threads:[~2010-05-22 13:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-21 13:26 [PATCH RFC] Add a config verbose option fetch and push Nathan W. Panike
2010-05-21 17:10 ` Ævar Arnfjörð Bjarmason
2010-05-22 10:44 ` Thomas Rast
2010-05-22 12:01 ` Ævar Arnfjörð Bjarmason
2010-05-22 13:34 ` Thomas Rast [this message]
2010-05-22 14:15 ` Ævar Arnfjörð Bjarmason
-- strict thread matches above, loose matches on Subject: below --
2010-05-21 13:26 Nathan W. Panike
2010-05-21 14:53 ` Peter Kjellerstedt
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=201005221534.18529.trast@student.ethz.ch \
--to=trast@student.ethz.ch \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=nathan.panike@gmail.com \
--cc=peter.kjellerstedt@axis.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.