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

Re: [RFH] How to get git-gui.sh history

From
MCMarco Costalba <mcostalba@gmail.com>
Date
Apr 21, 2007, 17:19 UTC
Message-ID
<e5bfff550704211019w67cb128ajba0bd1a6b56ada3a@mail.gmail.com>
In-Reply-To
<Pine.LNX.4.64.0704211703340.20005@beast.quantumfyre.co.uk>
On 4/21/07, Julian Phillips <julian@quantumfyre.co.uk> wrote:
Show 15 quoted lines
> On Sat, 21 Apr 2007, Michael wrote:
>
> > Marco Costalba wrote:
> >> On 4/21/07, Junio C Hamano <junkio@cox.net> wrote:
> >>> "Marco Costalba" <mcostalba@gmail.com> writes:
> >>>
> >>> $ git rev-list -- git-gui.sh | wc -l
> >>> 158
> >>>
> >>
> >> This is strange....
>
> try git rev-list --all --full-history -- git-gui.sh | wc -l, that gives
> 158 for me (in the git repo) ...
>

Yes, --full-history here is the missed link here, it works also with just HEAD instead of --all

$ git rev-list HEAD --full-history -- git-gui.sh | wc -l 158

Unfortunatly this is much slower,

$ time git rev-list HEAD --full-history -- git-gui.sh > /dev/null 1.77user 0.03system 0:01.88elapsed 95%CPU (0avgtext+0avgdata 0maxresident)k 0inputs+0outputs (0major+4030minor)pagefaults 0swaps

$ time git rev-list HEAD -- git-gui.sh > /dev/null 0.80user 0.02system 0:00.91elapsed 91%CPU (0avgtext+0avgdata 0maxresident)k 0inputs+0outputs (0major+3382minor)pagefaults 0swaps

   Marco
Previous: Julian PhillipsNext: Michael
Message 6 of 7 in “[RFH] How to get git-gui.sh history”
  1. Marco CostalbaApr 21, 2007
  2. Junio C HamanoApr 21, 2007
  3. Marco CostalbaApr 21, 2007
  4. MichaelApr 21, 2007
  5. Julian PhillipsApr 21, 2007
  6. Marco CostalbaApr 21, 2007
  7. MichaelApr 21, 2007

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.