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, 16:54 UTC
Message-ID
<xmqqr3nh4qx5.fsf@gitster.dls.corp.google.com>
In-Reply-To
<1438784487-9176-1-git-send-email-avarab@gmail.com>
Ævar Arnfjörð Bjarmason  <avarab@gmail.com> writes:
Show 10 quoted lines
> When you look at the history for a file via "git log" we don't show
> --full-history by default, but the Gitweb UI does so, which can be very
> confusing for all the reasons discussed in "History Simplification" in
> git-log(1) and in
> http://thread.gmane.org/gmane.comp.version-control.git/89400/focus=90659
>
> We've been doing history via --full-history since pretty much forever,
> but I think this is much more usable, and on a typical project with lots
> of branches being merged it makes for a much less confusing view. We do
> this for git log by default, why wouldn't Gitweb follow suit?
http://thread.gmane.org/gmane.comp.version-control.git/89400/focus=90758

seems to agree with you in principle that this would be what gitweb should do if it were written today.

Previous: Ævar Arnfjörð BjarmasonNext: Ævar Arnfjörð Bjarmason
Message 2 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.