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

Re: how to display file history?

From
MCMarco Costalba <mcostalba@gmail.com>
Date
May 15, 2006, 18:32 UTC
Message-ID
<e5bfff550605151132s4605a241sd3132aaeb2de6a39@mail.gmail.com>
In-Reply-To
<Pine.LNX.4.64.0605151055080.3866@g5.osdl.org>
On 5/15/06, Linus Torvalds <torvalds@osdl.org> wrote:
Show 8 quoted lines
>
>
> qgit would seem to prefer to have the commit counting only affect the
> "primary" commits, and not the "boundary" ones at all. Which might be
> sensible, but it's not the semantics it has now.
>
> gitk doesn't care, because it uses the boundary commits just as hints.
>
$ git-rev-list --topo-order --after="Apr 10" --before="Apr 11" HEAD |wc
     14      14     574
$ git-rev-list --topo-order --boundary --after="Apr 10" --before="Apr
11" HEAD |wc
     18      18     742

Boundary revisions in this case are _not_ passed through search filtering. Using --boundary option we get revisions ouside given filter range.

This does not apply to our previous example. So at least --boundary behaviour it's a little bit inconsistent at the moment.

        Marco
Previous: Linus TorvaldsNext: Linus Torvalds
Message 11 of 12 in “RE: how to display file history?”
  1. Brown, LenMay 15, 2006
  2. Junio C HamanoMay 15, 2006
  3. Eric W. BiedermanMay 15, 2006
  4. Linus TorvaldsMay 15, 2006
  5. Eric W. BiedermanMay 15, 2006
  6. Linus TorvaldsMay 15, 2006
  7. J. Bruce FieldsMay 15, 2006
  8. Jonas FonsecaMay 21, 2006
  9. Marco CostalbaMay 15, 2006
  10. Linus TorvaldsMay 15, 2006
  11. Marco CostalbaMay 15, 2006
  12. Linus TorvaldsMay 15, 2006

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.