git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH/RFC] gitweb: Don't pass --full-history to git-log(1)

From
Junio C Hamano <gitster@pobox.com>
Date
Aug 5, 2015, 21:45 UTC
Message-ID
<xmqqvbct1kb3.fsf@gitster.dls.corp.google.com>
In-Reply-To
<CACBZZX5GvCqx3LkWBDb4kDFpyaEwK-Fnhtof6nhKsctmx22m1g@mail.gmail.com>
Ævar Arnfjörð Bjarmason <avarab@gmail.com> writes:
Show 5 quoted lines
> I'm reminded of the make(1) story about not supporting spaces instead
> of tabs because the guy already had a few dozen users.
>
> We could have changed this in 2008, when Git already had much fewer
> users,
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.

Previous: Ævar Arnfjörð BjarmasonNext: Junio C Hamano
Message 4 of 5 in “gitweb: Don't pass --full-history to git-log(1)”
  1. gitweb: Don't pass --full-history to git-log(1)Ævar Arnfjörð Bjarmason, Aug 5, 2015
  2. Junio C HamanoAug 5, 2015
  3. Ævar Arnfjörð BjarmasonAug 5, 2015
  4. Junio C HamanoAug 5, 2015
  5. Junio C HamanoAug 6, 2015

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.