From: Linus Torvalds <torvalds@osdl.org>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Carl Baldwin <cnb@fc.hp.com>, Junio C Hamano <junkio@cox.net>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH 2/3] sha1_file: add the ability to parse objects in "pack file format"
Date: Tue, 11 Jul 2006 11:58:24 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0607111153170.5623@g5.osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.63.0607112031150.29667@wbgn013.biozentrum.uni-wuerzburg.de>
On Tue, 11 Jul 2006, Johannes Schindelin wrote:
>
> Why not just say
>
> return *hdr ? -1 : bytes;
Hey, whatever works. I rewrote more, and edited some of my changes down
again..
> You might want to add a comment saying "since the type is lowercase in
> ascii format, object_type must be 6 or 7, which is an invalid object
> type." It took me a little to figure that out...
It's not even correct in my version - I check the ASCII header _first_, so
by the time it looks at the binary one, it already knows it's not ascii.
The problematic case is actually the other way around: my
"parse_ascii_sha1_header()" isn't strict enough.
Or, more likely, the parse_sha1_header() function should just be changed
to check the binary format first (and then add your comment about why that
is safe).
> > + bits = 4;
> > + while (!(c & 0x80)) {
> > + if (bits >= 8*sizeof(unsigned long))
> > + return -1;
> > + c = *hdr++;
> > + size += (unsigned long) (c & 0x7f) << bits;
> > + bytes++;
> > + bits += 7;
> > + }
>
> Are you not losing the last byte by putting the "while" _before_ instead
> of _after_ the loop?
No. The very first byte can have the 0x80 end marker, when the size was
between 0..15.
> > int sha1_object_info(const unsigned char *sha1, char *type, unsigned long *sizep)
> > {
> > - int status;
> > + int status, hdrlen;
> > unsigned long mapsize, size;
> > void *map;
> > z_stream stream;
>
> This hunk is unnecessary, right?
Yeah, never mind. That function didn't actually need the hdrlen, it only
cared about the SHA1.
Linus
next prev parent reply other threads:[~2006-07-11 19:05 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-10 23:01 Revisiting large binary files issue Carl Baldwin
2006-07-10 23:14 ` Junio C Hamano
2006-07-11 6:20 ` Peter Baumann
2006-07-10 23:28 ` Linus Torvalds
2006-07-11 9:40 ` [RFC]: Pack-file object format for individual objects (Was: Revisiting large binary files issue.) sf
2006-07-11 18:00 ` Linus Torvalds
2006-07-11 21:45 ` sf
2006-07-11 22:17 ` Linus Torvalds
2006-07-11 22:26 ` Linus Torvalds
2006-07-11 14:55 ` Revisiting large binary files issue Carl Baldwin
2006-07-11 17:09 ` Linus Torvalds
2006-07-11 17:10 ` [PATCH 1/3] Make the unpacked object header functions static to sha1_file.c Linus Torvalds
2006-07-11 17:12 ` [PATCH 2/3] sha1_file: add the ability to parse objects in "pack file format" Linus Torvalds
2006-07-11 18:40 ` Johannes Schindelin
2006-07-11 18:58 ` Linus Torvalds [this message]
2006-07-11 19:20 ` Johannes Schindelin
2006-07-11 19:48 ` Linus Torvalds
2006-07-11 21:25 ` Johannes Schindelin
2006-07-11 21:47 ` Junio C Hamano
2006-07-11 21:24 ` sf
2006-07-11 22:09 ` Linus Torvalds
2006-07-11 22:25 ` sf
2006-07-11 23:03 ` Junio C Hamano
2006-07-12 0:03 ` Linus Torvalds
2006-07-12 0:39 ` Johannes Schindelin
2006-07-12 3:45 ` Linus Torvalds
2006-07-12 4:31 ` Linus Torvalds
2006-07-12 6:35 ` Junio C Hamano
2006-07-12 16:29 ` Linus Torvalds
2006-07-12 0:46 ` Junio C Hamano
2006-07-12 3:42 ` Linus Torvalds
2006-07-12 6:49 ` Peter Baumann
2006-07-12 7:16 ` Junio C Hamano
2006-07-12 8:28 ` Peter Baumann
2006-07-12 15:13 ` Linus Torvalds
2006-07-12 15:27 ` Junio C Hamano
2006-07-11 17:16 ` [PATCH 3/3] Enable the new binary header format for unpacked objects Linus Torvalds
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.64.0607111153170.5623@g5.osdl.org \
--to=torvalds@osdl.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=cnb@fc.hp.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).