git/builtin-pack-objects.c, branch v1.5.2

Increase pack.depth default to 50

2007-05-09T05:47:17Z

Signed-off-by: "Theodore Ts'o" Signed-off-by: Junio C Hamano

Add pack.depth option to git-pack-objects.

2007-05-09T05:47:17Z

Signed-off-by: "Theodore Ts'o" Signed-off-by: Junio C Hamano

Use GIT_OBJECT_DIR for temporary files of pack-objects

2007-05-07T22:45:24Z

Signed-off-by: Alex Riesen Signed-off-by: Junio C Hamano

make progress "title" part of the common progress interface

2007-04-23T05:18:05Z

If the progress bar ends up in a box, better provide a title for it too. Signed-off-by: Nicolas Pitre Signed-off-by: Junio C Hamano

common progress display support

2007-04-23T05:18:05Z

Instead of having this code duplicated in multiple places, let's have a common interface for progress display. If someday someone wishes to display a cheezy progress bar instead then only one file will have to be changed. Note: I left merge-recursive.c out since it has a strange notion of progress as it apparently increase the expected total number as it goes. Someone with more intimate knowledge of what that is supposed to mean might look at converting it to the common progress interface. Signed-off-by: Nicolas Pitre Signed-off-by: Junio C Hamano

pack-objects: make generated packfile read-only

2007-04-23T02:00:16Z

Signed-off-by: Junio C Hamano

Fix 'quickfix' on pack-objects.

2007-04-22T19:28:34Z

The earlier quickfix forced world-readable permission bits. This updates it to honor umask and core.sharedrepository settings. Signed-off-by: Junio C Hamano

pack-objects: quickfix for permission modes.

2007-04-22T18:49:35Z

mkstemp() often creates the file in 0600 which means the resulting packfile is not readable by anybody other than the repository owner. Force 0644 for now, even though this is not strictly correct. Signed-off-by: Junio C Hamano

pack-objects: remove obsolete comments

2007-04-20T03:37:41Z

The sorted-by-sha ans sorted-by-type arrays are no more. Signed-off-by: Nicolas Pitre Signed-off-by: Junio C Hamano

pack-objects: better check_object() performances

2007-04-17T00:43:31Z

With large amount of objects, check_object() is really trashing the pack sliding map and the filesystem cache. It has a completely random access pattern especially with old objects where delta replay jumps back and forth all over the pack. This patch improves things by: 1) sorting objects by their offset in pack before calling check_object() so the pack access pattern is linear; 2) recording the object type at add_object_entry() time since it is already known in most cases; 3) recording the pack offset even for preferred_base objects; 4) avoid calling sha1_object_info() if all possible. This limits pack accesses to the bare minimum and makes them perfectly linear. In the process check_object() was made more clear (to me at least). Note: I thought about walking the sorted_by_offset list backward in get_object_details() so if a pack happens to be larger than the available file cache, then the cache would have been populated with useful data from the beginning of the pack already when find_deltas() is called. Strangely, testing (on Linux) showed absolutely no performance difference. Signed-off-by: Nicolas Pitre Signed-off-by: Junio C Hamano