user/sven/git.git/git-repack.sh, branch v1.5.0.7

[PATCH] Rename git-repo-config to git-config.

2007-01-29T00:16:53Z

Signed-off-by: Tom Prince Signed-off-by: Junio C Hamano

Make git-prune-packed a bit more chatty.

2007-01-12T23:10:29Z

Steven Grimm noticed that git-repack's verbosity is inconsistent because pack-objects is chatty and prune-packed is not. This makes the latter a bit more chatty and gives -q option to squelch it. Signed-off-by: Junio C Hamano

Teach git-repack to preserve objects referred to by reflog entries.

2006-12-21T01:22:10Z

This adds a new option --reflog to pack-objects and revision machinery; do not bother documenting it for now, since this is only useful for local repacking. When the option is passed, objects reachable from reflog entries are marked as interesting while computing the set of objects to pack. Signed-off-by: Junio C Hamano

repacked packs should be read-only

2006-12-13T22:18:16Z

... just like the other pack creating tools do. Signed-off-by: Nicolas Pitre Signed-off-by: Junio C Hamano

Only repack active packs by skipping over kept packs.

2006-10-29T20:46:21Z

During `git repack -a -d` only repack objects which are loose or which reside in an active (a non-kept) pack. This allows the user to keep large packs as-is without continuous repacking and can be very helpful on large repositories. It should also help us resolve a race condition between `git repack -a -d` and the new pack store functionality in `git-receive-pack`. Kept packs are those which have a corresponding .keep file in $GIT_OBJECT_DIRECTORY/pack. That is pack-X.pack will be kept (not repacked and not deleted) if pack-X.keep exists in the same directory when `git repack -a -d` starts. Currently this feature is not documented and there is no user interface to keep an existing pack. Signed-off-by: Shawn O. Pearce Signed-off-by: Junio C Hamano

Merge branch 'np/pack'

2006-10-23T05:51:42Z

* np/pack: add the capability for index-pack to read from a stream index-pack: compare only the first 20-bytes of the key. git-repack: repo.usedeltabaseoffset pack-objects: document --delta-base-offset option allow delta data reuse even if base object is a preferred base zap a debug remnant let the GIT native protocol use offsets to delta base when possible make pack data reuse compatible with both delta types make git-pack-objects able to create deltas with offset to base teach git-index-pack about deltas with offset to base teach git-unpack-objects about deltas with offset to base introduce delta objects with offset to base

git-repack: repo.usedeltabaseoffset

2006-10-14T04:28:58Z

When configuration variable `repack.UseDeltaBaseOffset` is set for the repository, the command passes `--delta-base-offset` option to `git-pack-objects`; this typically results in slightly smaller packs, but the generated packs are incompatible with versions of git older than (and including) v1.4.3. We will make it default to true sometime in the future, but not for a while. Signed-off-by: Junio C Hamano

git-repack: allow git-repack to run in subdirectory

2006-09-25T03:16:23Z

Now that we explicitly create all tmpfiles below $GIT_DIR, there's no reason to care about which directory we're in. Signed-off-by: Jeff King Signed-off-by: Junio C Hamano

repack: use only pack-objects, not rev-list.

2006-09-20T18:15:32Z

Signed-off-by: Junio C Hamano

git-repack: create new packs inside $GIT_DIR, not cwd

2006-09-06T07:21:57Z

Avoid failing when cwd is !writable by writing the packfiles in $GIT_DIR, which is more in line with other commands. Without this, git-repack was failing when run from crontab by non-root user accounts. For large repositories, this also makes the mv operation a lot cheaper, and avoids leaving temp packfiles around the fs upon failure. Signed-off-by: Martin Langhoff Signed-off-by: Junio C Hamano