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 12:44:31 +0200 [thread overview]
Message-ID: <201005221244.32213.trast@student.ethz.ch> (raw)
In-Reply-To: <AANLkTil-PDpdkcJaJn2FUrJrSIJ6lP0OcvY5l7HRorsa@mail.gmail.com>
Ævar Arnfjörð Bjarmason wrote:
> Since Peter Kjellerstedt wanted --ff-only, and you want --verbose. I
> wonder whether a better solution wouldn't be to farm this
> functionality out to the config parser.
[...]
> [fetch "option"]
> verbose = 1
>
> Is there any reason not to add such a general facility?
That would completely ruin the scriptability of almost all commands.
Imagine the user added the following options as default:
add --edit
checkout --patch
cherry-pick --no-commit
commit --amend
pull --rebase
I'm sure you can find one option that changes the command in something
completely different *for every command*.
In fact even pull --ff-only has the same problem since it will refuse
the merge in cases where an unmodified pull would go through.
--
Thomas Rast
trast@{inf,student}.ethz.ch
next prev parent reply other threads:[~2010-05-22 10:45 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 [this message]
2010-05-22 12:01 ` Ævar Arnfjörð Bjarmason
2010-05-22 13:34 ` Thomas Rast
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=201005221244.32213.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.