git, branch v0.99

[PATCH] alternate object store and fsck

2005-07-10T23:16:34Z

The location alt_odb[j].name[0..] is filled with ??/?{38} to form a sha1 filename to try, but I was too lazy to allocate a copy, so while fsck_object_dir() is running for the directory, the filenames ??/?{38} are filled after NUL (usually and always the location should have '/'), making them "not found". This should fix it. Signed-off-by: Linus Torvalds

Fix up progress report for off-by-one error

2005-07-10T23:14:22Z

We used to print the index of the object we unpacked, not how many we had unpacked. Which caused slightly confusing progress reports like 100% (2/3) done rather than the more obvious "3/3" for 100% ;)

Make "git log" exit properly if not in a git archive

2005-07-10T23:10:21Z

Instead of getting an incomprehensible error message from git-rev-list.

Avoid signedness warnings in sha1_file.c

2005-07-10T22:43:54Z

Very irritating. But "snprintf()" wants "char *", and zlib wants "unsigned char *".

[PATCH] Remove map_sha1_file

2005-07-10T22:39:08Z

Remove map_sha1_file(), now unused. Signed-off-by: Daniel Barkalow Signed-off-by: Linus Torvalds

[PATCH] write_sha1_to_fd()

2005-07-10T22:39:08Z

Add write_sha1_to_fd(), which writes an object to a file descriptor. This includes support for unpacking it and recompressing it. Signed-off-by: Daniel Barkalow Signed-off-by: Linus Torvalds

git-rev-list: allow missing objects when the parent is marked UNINTERESTING

2005-07-10T22:09:46Z

We still want the "top-most" uninteresting object to exist, so that we know that we have reached it.

Add "-q" flag to "git commit"

2005-07-09T17:52:35Z

Maybe you don't want the progress report.

git-unpack-objects: show progress report by default

2005-07-09T17:43:02Z

This ends up being very calming for big "git clone"s, since otherwise you just get very frustrated with a long silence, wondering whether it's working at all. Use "-q" to quiet it down. Now if we could just do the same for the initial "figure out what to pack" phase, which can also be quite slow if the other end is busy (or not packed and not in cache)...

[PATCH] format-patch: fix skipping of blank-lines

2005-07-09T02:48:44Z

If it is fed a commit with more than one leading blank lines, the sed scripts git-format-patch-script used looped forever. Using git-stripspace upfront makes the sed script somewhat simpler to work around this problem. Also use git-rev-parse so that we can say $ git-format-patch-script HEAD^^^^ to prepare the latest four patches for e-mail submission. Signed-off-by: Junio C Hamano Signed-off-by: Linus Torvalds