From: Junio C Hamano <gitster@pobox.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: Git <git@vger.kernel.org>
Subject: Re: [PATCH/RFC] gitweb: Don't pass --full-history to git-log(1)
Date: Thu, 06 Aug 2015 00:41:05 -0700 [thread overview]
Message-ID: <xmqqy4hozwxa.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <xmqqvbct1kb3.fsf@gitster.dls.corp.google.com> (Junio C. Hamano's message of "Wed, 05 Aug 2015 14:45:20 -0700")
Junio C Hamano <gitster@pobox.com> writes:
> Heh, in 2008 we already had more than a few dozen.
>
> I think
>
> (1) It is perfectly OK to add an UI option to let the web visitor
> choose between simplified and full history at runtime,
> optionally with a new gitweb.conf option to let the project
> owner choose which one is the default;
>
> (2) It is also OK to add gitweb.conf option to let the project/site
> choose between the two, optionally allowing the web visitor to
> override it with something like (1).
>
> Anything else would not give the same out-of-the-box experience and
> would probably not fly well.
Just to make sure, "would not fly well" is not an outright rejection
(given enough thrust, even a pig could fly).
An alternative with a bit more friction may be to do a variant of
(2), without UI but only with gitweb.conf tweakability, _and_
flipped default. That will break the out-of-the-box experience but
I suspect that many people would not notice (because their history
is linear), some people who do notice would like the change, and the
remainder can tweak their installation back to the full-history
version, as long the change of the default is prominently
advertised.
prev parent reply other threads:[~2015-08-06 7:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-05 14:21 [PATCH/RFC] gitweb: Don't pass --full-history to git-log(1) Ævar Arnfjörð Bjarmason
2015-08-05 16:54 ` Junio C Hamano
2015-08-05 21:28 ` Ævar Arnfjörð Bjarmason
2015-08-05 21:45 ` Junio C Hamano
2015-08-06 7:41 ` Junio C Hamano [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=xmqqy4hozwxa.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=avarab@gmail.com \
--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 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.