From: Linus Torvalds <torvalds@osdl.org>
To: Daniel Barkalow <barkalow@iabervon.org>
Cc: Petr Baudis <pasky@ucw.cz>, git@vger.kernel.org
Subject: Re: [0/5] Parsers for git objects, porting some programs
Date: Mon, 18 Apr 2005 11:34:35 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.58.0504181126480.15725@ppc970.osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.21.0504172229240.30848-100000@iabervon.org>
On Sun, 17 Apr 2005, Daniel Barkalow wrote:
>
> This series introduces common parsers for objects, and ports the programs
> that currently use revision.h to them.
>
> 1: the header files
> 2: the implementations
> 3: port rev-tree
> 4: port fsck-cache
> 5: port merge-base
Ok, having now looked at the code, I don't have any objections at all.
Could you clarify the "fsck" issue about reading the same object twice?
When does that happen?
Linus
next prev parent reply other threads:[~2005-04-18 18:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-18 0:25 [RFC] General object parsing Daniel Barkalow
2005-04-18 1:15 ` Linus Torvalds
2005-04-18 2:15 ` Daniel Barkalow
2005-04-18 2:33 ` [0/5] Parsers for git objects, porting some programs Daniel Barkalow
2005-04-18 2:35 ` [1/5] Header files for object parsing Daniel Barkalow
2005-04-18 2:36 ` [2/5] Implementations of parsing functions Daniel Barkalow
2005-04-18 2:37 ` [3/5] Port rev-tree to " Daniel Barkalow
2005-04-18 2:40 ` [4/5] Port fsck-cache to use " Daniel Barkalow
2005-04-18 2:42 ` [5/5] Switch implementations of merge-base, port to parsing Daniel Barkalow
2005-04-18 18:34 ` Linus Torvalds [this message]
2005-04-18 20:12 ` [0/5] Parsers for git objects, porting some programs Daniel Barkalow
2005-04-19 1:15 ` Junio C Hamano
2005-04-19 1:23 ` Daniel Barkalow
2005-04-19 2:04 ` Daniel Barkalow
2005-04-18 3:51 ` [RFC] General object parsing Daniel Barkalow
2005-04-18 4:45 ` David Woodhouse
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.58.0504181126480.15725@ppc970.osdl.org \
--to=torvalds@osdl.org \
--cc=barkalow@iabervon.org \
--cc=git@vger.kernel.org \
--cc=pasky@ucw.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).