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

Re: [RFC] General object parsing

From
Daniel Barkalow <barkalow@iabervon.org>
Date
Apr 18, 2005, 02:15 UTC
Message-ID
<Pine.LNX.4.21.0504172206460.30848-100000@iabervon.org>
In-Reply-To
<Pine.LNX.4.58.0504171807590.7211@ppc970.osdl.org>
On Sun, 17 Apr 2005, Linus Torvalds wrote:
Show 8 quoted lines
> On Sun, 17 Apr 2005, Daniel Barkalow wrote:
> > 
> > Any comment on the design, or should I send my implementation?
> 
> Show the patches, and maybe I (and others) can make comments on the 
> thing.. It doesn't sound broken by design, the only question is how much 
> harder (if any) it is to use than the rather trivial "revision.h" which 
> gets us really small files.

I don't think it's much different in difficulty, plus it handles more (parsing the objects more completely). They'll follow.

> In particular, is there some easy way to walk backwards by time? "git log"  
> definitely needs that, and merge-base clearly wants something similar. I
> also pretty much guarantee that visualization tools want that - creating a
> visual representation of the dag by time.

I think that should be easy, although I haven't written code to do it. If you output the whole history, sorted by date, you obviously need to get the whole history, but I expect people will have some sort of pruning to keep it down to a size they care about.

> But if there are simple helper functions to get the "next backwards in 
> time" case (by looking at the parent dates in a merge), then that should 
> be ok to do incrementally.
Haven't written that yet, but I can do so.
	-Daniel
*This .sig left intentionally blank*
Previous: Linus TorvaldsNext: Daniel Barkalow
Message 3 of 16 in “[RFC] General object parsing”
  1. Daniel BarkalowApr 18, 2005
  2. Linus TorvaldsApr 18, 2005
  3. Daniel BarkalowApr 18, 2005
  4. 0/5 Parsers for git objects, porting some programsDaniel Barkalow, Apr 18, 2005
  5. 1/5 Header files for object parsingDaniel Barkalow, Apr 18, 2005
  6. 2/5 Implementations of parsing functionsDaniel Barkalow, Apr 18, 2005
  7. 3/5 Port rev-tree to parsing functionsDaniel Barkalow, Apr 18, 2005
  8. 4/5 Port fsck-cache to use parsing functionsDaniel Barkalow, Apr 18, 2005
  9. 5/5 Switch implementations of merge-base, port to parsingDaniel Barkalow, Apr 18, 2005
  10. Linus TorvaldsApr 18, 2005
  11. Daniel BarkalowApr 18, 2005
  12. Junio C HamanoApr 19, 2005
  13. Daniel BarkalowApr 19, 2005
  14. Daniel BarkalowApr 19, 2005
  15. Daniel BarkalowApr 18, 2005
  16. David WoodhouseApr 18, 2005

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.