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

Re: [PATCH 1/5] Introduces for_each_revision() helper

From
Junio C Hamano <junkio@cox.net>
Date
Apr 30, 2007, 23:19 UTC
Message-ID
<7vps5lbgd3.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<20070429070616.GV5942@spearce.org>
"Shawn O. Pearce" <spearce@spearce.org> writes:
Show 5 quoted lines
> But in_merge_base is heavyweight if the two commits are in the
> same object database, but aren't connected at all.  You'll need
> to traverse both histories before aborting and saying there is
> no merge base.  That ain't cheap on large trees.  But its also a
> single line of code.

Who said anything about "a single line of code"? That is quite different from heaviness hidden in a control structure lookalike.

Previous: Shawn O. PearceNext: Johannes Schindelin
Message 7 of 17 in “New for_each_revision() helper”
  1. 0/5 New for_each_revision() helperLuiz Fernando N. Capitulino, Apr 27, 2007
  2. 1/5 Introduces for_each_revision() helperLuiz Fernando N. Capitulino, Apr 27, 2007
  3. Junio C HamanoApr 27, 2007
  4. Luiz Fernando N. CapitulinoApr 27, 2007
  5. Junio C HamanoApr 29, 2007
  6. Shawn O. PearceApr 29, 2007
  7. Junio C HamanoApr 30, 2007
  8. Johannes SchindelinApr 28, 2007
  9. Alex RiesenApr 28, 2007
  10. Johannes SchindelinApr 28, 2007
  11. Luiz Fernando N. CapitulinoApr 28, 2007
  12. Alex RiesenApr 28, 2007
  13. Luiz Fernando N. CapitulinoApr 29, 2007
  14. 2/5 builtin-fmt-merge-msg.c: Use for_each_revision() helperLuiz Fernando N. Capitulino, Apr 27, 2007
  15. 3/5 reachable.c: Use for_each_revision() helperLuiz Fernando N. Capitulino, Apr 27, 2007
  16. 4/5 builtin-shortlog.c: Use for_each_revision() helperLuiz Fernando N. Capitulino, Apr 27, 2007
  17. 5/5 builtin-log.c: Use for_each_revision() helperLuiz Fernando N. Capitulino, Apr 27, 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.