2006-07-07 01:16:22 +08:00
|
|
|
#include "cache.h"
|
|
|
|
|
#include "commit.h"
|
|
|
|
|
#include "diff.h"
|
2023-03-21 14:26:03 +08:00
|
|
|
#include "environment.h"
|
2023-03-21 14:25:54 +08:00
|
|
|
#include "gettext.h"
|
2023-02-24 08:09:27 +08:00
|
|
|
#include "hex.h"
|
2006-07-07 01:16:22 +08:00
|
|
|
#include "revision.h"
|
|
|
|
|
#include "builtin.h"
|
2007-01-06 18:16:17 +08:00
|
|
|
#include "reachable.h"
|
2008-03-24 04:50:29 +08:00
|
|
|
#include "parse-options.h"
|
2011-11-05 20:00:08 +08:00
|
|
|
#include "progress.h"
|
2020-03-24 09:07:52 +08:00
|
|
|
#include "prune-packed.h"
|
2023-02-24 08:09:33 +08:00
|
|
|
#include "replace-object.h"
|
2023-04-11 15:41:49 +08:00
|
|
|
#include "object-name.h"
|
2018-05-16 07:42:15 +08:00
|
|
|
#include "object-store.h"
|
2020-05-01 03:48:50 +08:00
|
|
|
#include "shallow.h"
|
2006-07-07 01:16:22 +08:00
|
|
|
|
2008-03-24 04:50:29 +08:00
|
|
|
static const char * const prune_usage[] = {
|
2017-11-21 23:51:52 +08:00
|
|
|
N_("git prune [-n] [-v] [--progress] [--expire <time>] [--] [<head>...]"),
|
2008-03-24 04:50:29 +08:00
|
|
|
NULL
|
|
|
|
|
};
|
2006-08-16 01:23:48 +08:00
|
|
|
static int show_only;
|
2008-09-30 00:49:52 +08:00
|
|
|
static int verbose;
|
2017-04-27 03:29:31 +08:00
|
|
|
static timestamp_t expire;
|
2011-11-08 13:34:08 +08:00
|
|
|
static int show_progress = -1;
|
2006-07-07 01:16:22 +08:00
|
|
|
|
2013-12-18 07:22:31 +08:00
|
|
|
static int prune_tmp_file(const char *fullpath)
|
2008-07-25 06:41:12 +08:00
|
|
|
{
|
2010-02-27 11:50:02 +08:00
|
|
|
struct stat st;
|
|
|
|
|
if (lstat(fullpath, &st))
|
|
|
|
|
return error("Could not stat '%s'", fullpath);
|
|
|
|
|
if (st.st_mtime > expire)
|
|
|
|
|
return 0;
|
2021-12-07 06:05:04 +08:00
|
|
|
if (S_ISDIR(st.st_mode)) {
|
|
|
|
|
if (show_only || verbose)
|
|
|
|
|
printf("Removing stale temporary directory %s\n", fullpath);
|
|
|
|
|
if (!show_only) {
|
|
|
|
|
struct strbuf remove_dir_buf = STRBUF_INIT;
|
|
|
|
|
|
|
|
|
|
strbuf_addstr(&remove_dir_buf, fullpath);
|
|
|
|
|
remove_dir_recursively(&remove_dir_buf, 0);
|
|
|
|
|
strbuf_release(&remove_dir_buf);
|
|
|
|
|
}
|
|
|
|
|
} else {
|
|
|
|
|
if (show_only || verbose)
|
|
|
|
|
printf("Removing stale temporary file %s\n", fullpath);
|
|
|
|
|
if (!show_only)
|
|
|
|
|
unlink_or_warn(fullpath);
|
|
|
|
|
}
|
2008-07-25 06:41:12 +08:00
|
|
|
return 0;
|
|
|
|
|
}
|
|
|
|
|
|
prune: lazily perform reachability traversal
The general strategy of "git prune" is to do a full reachability walk,
then for each loose object see if we found it in our walk. But if we
don't have any loose objects, we don't need to do the expensive walk in
the first place.
This patch postpones that walk until the first time we need to see its
results.
Note that this is really a specific case of a more general optimization,
which is that we could traverse only far enough to find the object under
consideration (i.e., stop the traversal when we find it, then pick up
again when asked about the next object, etc). That could save us in some
instances from having to do a full walk. But it's actually a bit tricky
to do with our traversal code, and you'd need to do a full walk anyway
if you have even a single unreachable object (which you generally do, if
any objects are actually left after running git-repack).
So in practice this lazy-load of the full walk catches one easy but
common case (i.e., you've just repacked via git-gc, and there's nothing
unreachable).
The perf script is fairly contrived, but it does show off the
improvement:
Test HEAD^ HEAD
-------------------------------------------------------------------------
5304.4: prune with no objects 3.66(3.60+0.05) 0.00(0.00+0.00) -100.0%
and would let us know if we accidentally regress this optimization.
Note also that we need to take special care with prune_shallow(), which
relies on us having performed the traversal. So this optimization can
only kick in for a non-shallow repository. Since this is easy to get
wrong and is not covered by existing tests, let's add an extra test to
t5304 that covers this case explicitly.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2019-02-14 12:35:22 +08:00
|
|
|
static void perform_reachability_traversal(struct rev_info *revs)
|
2006-07-07 01:16:22 +08:00
|
|
|
{
|
prune: lazily perform reachability traversal
The general strategy of "git prune" is to do a full reachability walk,
then for each loose object see if we found it in our walk. But if we
don't have any loose objects, we don't need to do the expensive walk in
the first place.
This patch postpones that walk until the first time we need to see its
results.
Note that this is really a specific case of a more general optimization,
which is that we could traverse only far enough to find the object under
consideration (i.e., stop the traversal when we find it, then pick up
again when asked about the next object, etc). That could save us in some
instances from having to do a full walk. But it's actually a bit tricky
to do with our traversal code, and you'd need to do a full walk anyway
if you have even a single unreachable object (which you generally do, if
any objects are actually left after running git-repack).
So in practice this lazy-load of the full walk catches one easy but
common case (i.e., you've just repacked via git-gc, and there's nothing
unreachable).
The perf script is fairly contrived, but it does show off the
improvement:
Test HEAD^ HEAD
-------------------------------------------------------------------------
5304.4: prune with no objects 3.66(3.60+0.05) 0.00(0.00+0.00) -100.0%
and would let us know if we accidentally regress this optimization.
Note also that we need to take special care with prune_shallow(), which
relies on us having performed the traversal. So this optimization can
only kick in for a non-shallow repository. Since this is easy to get
wrong and is not covered by existing tests, let's add an extra test to
t5304 that covers this case explicitly.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2019-02-14 12:35:22 +08:00
|
|
|
static int initialized;
|
|
|
|
|
struct progress *progress = NULL;
|
|
|
|
|
|
|
|
|
|
if (initialized)
|
|
|
|
|
return;
|
|
|
|
|
|
|
|
|
|
if (show_progress)
|
|
|
|
|
progress = start_delayed_progress(_("Checking connectivity"), 0);
|
|
|
|
|
mark_reachable_objects(revs, 1, expire, progress);
|
|
|
|
|
stop_progress(&progress);
|
|
|
|
|
initialized = 1;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
static int is_object_reachable(const struct object_id *oid,
|
|
|
|
|
struct rev_info *revs)
|
|
|
|
|
{
|
2019-02-14 12:38:21 +08:00
|
|
|
struct object *obj;
|
|
|
|
|
|
prune: lazily perform reachability traversal
The general strategy of "git prune" is to do a full reachability walk,
then for each loose object see if we found it in our walk. But if we
don't have any loose objects, we don't need to do the expensive walk in
the first place.
This patch postpones that walk until the first time we need to see its
results.
Note that this is really a specific case of a more general optimization,
which is that we could traverse only far enough to find the object under
consideration (i.e., stop the traversal when we find it, then pick up
again when asked about the next object, etc). That could save us in some
instances from having to do a full walk. But it's actually a bit tricky
to do with our traversal code, and you'd need to do a full walk anyway
if you have even a single unreachable object (which you generally do, if
any objects are actually left after running git-repack).
So in practice this lazy-load of the full walk catches one easy but
common case (i.e., you've just repacked via git-gc, and there's nothing
unreachable).
The perf script is fairly contrived, but it does show off the
improvement:
Test HEAD^ HEAD
-------------------------------------------------------------------------
5304.4: prune with no objects 3.66(3.60+0.05) 0.00(0.00+0.00) -100.0%
and would let us know if we accidentally regress this optimization.
Note also that we need to take special care with prune_shallow(), which
relies on us having performed the traversal. So this optimization can
only kick in for a non-shallow repository. Since this is easy to get
wrong and is not covered by existing tests, let's add an extra test to
t5304 that covers this case explicitly.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2019-02-14 12:35:22 +08:00
|
|
|
perform_reachability_traversal(revs);
|
2014-10-16 06:38:55 +08:00
|
|
|
|
2019-06-20 15:41:14 +08:00
|
|
|
obj = lookup_object(the_repository, oid);
|
2019-02-14 12:38:21 +08:00
|
|
|
return obj && (obj->flags & SEEN);
|
prune: lazily perform reachability traversal
The general strategy of "git prune" is to do a full reachability walk,
then for each loose object see if we found it in our walk. But if we
don't have any loose objects, we don't need to do the expensive walk in
the first place.
This patch postpones that walk until the first time we need to see its
results.
Note that this is really a specific case of a more general optimization,
which is that we could traverse only far enough to find the object under
consideration (i.e., stop the traversal when we find it, then pick up
again when asked about the next object, etc). That could save us in some
instances from having to do a full walk. But it's actually a bit tricky
to do with our traversal code, and you'd need to do a full walk anyway
if you have even a single unreachable object (which you generally do, if
any objects are actually left after running git-repack).
So in practice this lazy-load of the full walk catches one easy but
common case (i.e., you've just repacked via git-gc, and there's nothing
unreachable).
The perf script is fairly contrived, but it does show off the
improvement:
Test HEAD^ HEAD
-------------------------------------------------------------------------
5304.4: prune with no objects 3.66(3.60+0.05) 0.00(0.00+0.00) -100.0%
and would let us know if we accidentally regress this optimization.
Note also that we need to take special care with prune_shallow(), which
relies on us having performed the traversal. So this optimization can
only kick in for a non-shallow repository. Since this is easy to get
wrong and is not covered by existing tests, let's add an extra test to
t5304 that covers this case explicitly.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2019-02-14 12:35:22 +08:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
static int prune_object(const struct object_id *oid, const char *fullpath,
|
|
|
|
|
void *data)
|
|
|
|
|
{
|
|
|
|
|
struct rev_info *revs = data;
|
|
|
|
|
struct stat st;
|
|
|
|
|
|
|
|
|
|
if (is_object_reachable(oid, revs))
|
2014-10-16 06:38:55 +08:00
|
|
|
return 0;
|
|
|
|
|
|
|
|
|
|
if (lstat(fullpath, &st)) {
|
|
|
|
|
/* report errors, but do not stop pruning */
|
|
|
|
|
error("Could not stat '%s'", fullpath);
|
|
|
|
|
return 0;
|
|
|
|
|
}
|
2010-02-27 11:50:02 +08:00
|
|
|
if (st.st_mtime > expire)
|
|
|
|
|
return 0;
|
2008-09-30 00:49:52 +08:00
|
|
|
if (show_only || verbose) {
|
2018-04-26 02:20:59 +08:00
|
|
|
enum object_type type = oid_object_info(the_repository, oid,
|
|
|
|
|
NULL);
|
2017-02-22 07:47:35 +08:00
|
|
|
printf("%s %s\n", oid_to_hex(oid),
|
2018-02-15 02:59:24 +08:00
|
|
|
(type > 0) ? type_name(type) : "unknown");
|
2008-09-30 00:49:52 +08:00
|
|
|
}
|
|
|
|
|
if (!show_only)
|
2009-04-30 05:22:56 +08:00
|
|
|
unlink_or_warn(fullpath);
|
2006-07-07 01:16:22 +08:00
|
|
|
return 0;
|
|
|
|
|
}
|
|
|
|
|
|
2023-02-24 14:39:24 +08:00
|
|
|
static int prune_cruft(const char *basename, const char *path,
|
|
|
|
|
void *data UNUSED)
|
2006-07-07 01:16:22 +08:00
|
|
|
{
|
2014-10-16 06:38:55 +08:00
|
|
|
if (starts_with(basename, "tmp_obj_"))
|
|
|
|
|
prune_tmp_file(path);
|
|
|
|
|
else
|
|
|
|
|
fprintf(stderr, "bad sha1 file: %s\n", path);
|
2006-07-07 01:16:22 +08:00
|
|
|
return 0;
|
|
|
|
|
}
|
|
|
|
|
|
2023-02-24 14:39:24 +08:00
|
|
|
static int prune_subdir(unsigned int nr UNUSED, const char *path,
|
|
|
|
|
void *data UNUSED)
|
2006-07-07 01:16:22 +08:00
|
|
|
{
|
2014-10-16 06:38:55 +08:00
|
|
|
if (!show_only)
|
|
|
|
|
rmdir(path);
|
|
|
|
|
return 0;
|
2006-07-07 01:16:22 +08:00
|
|
|
}
|
|
|
|
|
|
2008-02-07 10:55:14 +08:00
|
|
|
/*
|
|
|
|
|
* Write errors (particularly out of space) can result in
|
|
|
|
|
* failed temporary packs (and more rarely indexes and other
|
2010-02-04 13:23:18 +08:00
|
|
|
* files beginning with "tmp_") accumulating in the object
|
2008-09-23 07:34:26 +08:00
|
|
|
* and the pack directories.
|
2008-02-07 10:55:14 +08:00
|
|
|
*/
|
2008-09-23 07:34:26 +08:00
|
|
|
static void remove_temporary_files(const char *path)
|
2008-02-07 10:55:14 +08:00
|
|
|
{
|
|
|
|
|
DIR *dir;
|
|
|
|
|
struct dirent *de;
|
|
|
|
|
|
2008-09-23 07:34:26 +08:00
|
|
|
dir = opendir(path);
|
2008-02-07 10:55:14 +08:00
|
|
|
if (!dir) {
|
2022-11-20 04:12:13 +08:00
|
|
|
if (errno != ENOENT)
|
|
|
|
|
fprintf(stderr, "Unable to open directory %s: %s\n",
|
|
|
|
|
path, strerror(errno));
|
2008-02-07 10:55:14 +08:00
|
|
|
return;
|
|
|
|
|
}
|
2008-07-25 06:41:12 +08:00
|
|
|
while ((de = readdir(dir)) != NULL)
|
2013-12-01 04:55:40 +08:00
|
|
|
if (starts_with(de->d_name, "tmp_"))
|
2013-12-18 07:22:31 +08:00
|
|
|
prune_tmp_file(mkpath("%s/%s", path, de->d_name));
|
2008-02-07 10:55:14 +08:00
|
|
|
closedir(dir);
|
|
|
|
|
}
|
|
|
|
|
|
2006-07-29 13:44:25 +08:00
|
|
|
int cmd_prune(int argc, const char **argv, const char *prefix)
|
2006-07-07 01:16:22 +08:00
|
|
|
{
|
2007-01-06 18:16:10 +08:00
|
|
|
struct rev_info revs;
|
2017-12-08 23:27:16 +08:00
|
|
|
int exclude_promisor_objects = 0;
|
2008-03-24 04:50:29 +08:00
|
|
|
const struct option options[] = {
|
2012-08-20 20:32:32 +08:00
|
|
|
OPT__DRY_RUN(&show_only, N_("do not remove, show only")),
|
|
|
|
|
OPT__VERBOSE(&verbose, N_("report pruned objects")),
|
|
|
|
|
OPT_BOOL(0, "progress", &show_progress, N_("show progress")),
|
2013-04-26 02:13:49 +08:00
|
|
|
OPT_EXPIRY_DATE(0, "expire", &expire,
|
|
|
|
|
N_("expire objects older than <time>")),
|
2017-12-08 23:27:16 +08:00
|
|
|
OPT_BOOL(0, "exclude-promisor-objects", &exclude_promisor_objects,
|
|
|
|
|
N_("limit traversal to objects outside promisor packfiles")),
|
2008-03-24 04:50:29 +08:00
|
|
|
OPT_END()
|
|
|
|
|
};
|
2008-09-23 07:34:26 +08:00
|
|
|
char *s;
|
2006-07-07 01:16:22 +08:00
|
|
|
|
2017-04-27 03:29:31 +08:00
|
|
|
expire = TIME_MAX;
|
2007-01-06 05:31:43 +08:00
|
|
|
save_commit_buffer = 0;
|
2018-07-19 04:45:20 +08:00
|
|
|
read_replace_refs = 0;
|
2018-09-21 23:57:38 +08:00
|
|
|
repo_init_revisions(the_repository, &revs, prefix);
|
2006-07-07 01:16:22 +08:00
|
|
|
|
2009-05-24 02:53:12 +08:00
|
|
|
argc = parse_options(argc, argv, prefix, options, prune_usage, 0);
|
2014-11-30 16:24:48 +08:00
|
|
|
|
2015-06-23 18:54:11 +08:00
|
|
|
if (repository_format_precious_objects)
|
|
|
|
|
die(_("cannot prune in a precious-objects repo"));
|
|
|
|
|
|
2008-03-25 14:20:51 +08:00
|
|
|
while (argc--) {
|
2017-05-01 10:28:58 +08:00
|
|
|
struct object_id oid;
|
2008-03-25 14:20:51 +08:00
|
|
|
const char *name = *argv++;
|
|
|
|
|
|
2023-03-28 21:58:46 +08:00
|
|
|
if (!repo_get_oid(the_repository, name, &oid)) {
|
object: convert parse_object* to take struct object_id
Make parse_object, parse_object_or_die, and parse_object_buffer take a
pointer to struct object_id. Remove the temporary variables inserted
earlier, since they are no longer necessary. Transform all of the
callers using the following semantic patch:
@@
expression E1;
@@
- parse_object(E1.hash)
+ parse_object(&E1)
@@
expression E1;
@@
- parse_object(E1->hash)
+ parse_object(E1)
@@
expression E1, E2;
@@
- parse_object_or_die(E1.hash, E2)
+ parse_object_or_die(&E1, E2)
@@
expression E1, E2;
@@
- parse_object_or_die(E1->hash, E2)
+ parse_object_or_die(E1, E2)
@@
expression E1, E2, E3, E4, E5;
@@
- parse_object_buffer(E1.hash, E2, E3, E4, E5)
+ parse_object_buffer(&E1, E2, E3, E4, E5)
@@
expression E1, E2, E3, E4, E5;
@@
- parse_object_buffer(E1->hash, E2, E3, E4, E5)
+ parse_object_buffer(E1, E2, E3, E4, E5)
Signed-off-by: brian m. carlson <sandals@crustytoothpaste.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2017-05-07 06:10:38 +08:00
|
|
|
struct object *object = parse_object_or_die(&oid,
|
|
|
|
|
name);
|
2008-03-25 14:20:51 +08:00
|
|
|
add_pending_object(&revs, object, "");
|
|
|
|
|
}
|
|
|
|
|
else
|
|
|
|
|
die("unrecognized argument: %s", name);
|
|
|
|
|
}
|
2011-11-08 13:34:08 +08:00
|
|
|
|
|
|
|
|
if (show_progress == -1)
|
|
|
|
|
show_progress = isatty(2);
|
2017-12-08 23:27:16 +08:00
|
|
|
if (exclude_promisor_objects) {
|
|
|
|
|
fetch_if_missing = 0;
|
|
|
|
|
revs.exclude_promisor_objects = 1;
|
|
|
|
|
}
|
2011-11-08 13:34:08 +08:00
|
|
|
|
2014-10-16 06:38:55 +08:00
|
|
|
for_each_loose_file_in_objdir(get_object_directory(), prune_object,
|
prune: lazily perform reachability traversal
The general strategy of "git prune" is to do a full reachability walk,
then for each loose object see if we found it in our walk. But if we
don't have any loose objects, we don't need to do the expensive walk in
the first place.
This patch postpones that walk until the first time we need to see its
results.
Note that this is really a specific case of a more general optimization,
which is that we could traverse only far enough to find the object under
consideration (i.e., stop the traversal when we find it, then pick up
again when asked about the next object, etc). That could save us in some
instances from having to do a full walk. But it's actually a bit tricky
to do with our traversal code, and you'd need to do a full walk anyway
if you have even a single unreachable object (which you generally do, if
any objects are actually left after running git-repack).
So in practice this lazy-load of the full walk catches one easy but
common case (i.e., you've just repacked via git-gc, and there's nothing
unreachable).
The perf script is fairly contrived, but it does show off the
improvement:
Test HEAD^ HEAD
-------------------------------------------------------------------------
5304.4: prune with no objects 3.66(3.60+0.05) 0.00(0.00+0.00) -100.0%
and would let us know if we accidentally regress this optimization.
Note also that we need to take special care with prune_shallow(), which
relies on us having performed the traversal. So this optimization can
only kick in for a non-shallow repository. Since this is easy to get
wrong and is not covered by existing tests, let's add an extra test to
t5304 that covers this case explicitly.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2019-02-14 12:35:22 +08:00
|
|
|
prune_cruft, prune_subdir, &revs);
|
2006-07-07 01:16:22 +08:00
|
|
|
|
2013-05-27 19:18:47 +08:00
|
|
|
prune_packed_objects(show_only ? PRUNE_PACKED_DRY_RUN : 0);
|
2008-09-23 07:34:26 +08:00
|
|
|
remove_temporary_files(get_object_directory());
|
2012-09-05 01:31:14 +08:00
|
|
|
s = mkpathdup("%s/pack", get_object_directory());
|
2008-09-23 07:34:26 +08:00
|
|
|
remove_temporary_files(s);
|
|
|
|
|
free(s);
|
2013-12-05 21:02:54 +08:00
|
|
|
|
prune: lazily perform reachability traversal
The general strategy of "git prune" is to do a full reachability walk,
then for each loose object see if we found it in our walk. But if we
don't have any loose objects, we don't need to do the expensive walk in
the first place.
This patch postpones that walk until the first time we need to see its
results.
Note that this is really a specific case of a more general optimization,
which is that we could traverse only far enough to find the object under
consideration (i.e., stop the traversal when we find it, then pick up
again when asked about the next object, etc). That could save us in some
instances from having to do a full walk. But it's actually a bit tricky
to do with our traversal code, and you'd need to do a full walk anyway
if you have even a single unreachable object (which you generally do, if
any objects are actually left after running git-repack).
So in practice this lazy-load of the full walk catches one easy but
common case (i.e., you've just repacked via git-gc, and there's nothing
unreachable).
The perf script is fairly contrived, but it does show off the
improvement:
Test HEAD^ HEAD
-------------------------------------------------------------------------
5304.4: prune with no objects 3.66(3.60+0.05) 0.00(0.00+0.00) -100.0%
and would let us know if we accidentally regress this optimization.
Note also that we need to take special care with prune_shallow(), which
relies on us having performed the traversal. So this optimization can
only kick in for a non-shallow repository. Since this is easy to get
wrong and is not covered by existing tests, let's add an extra test to
t5304 that covers this case explicitly.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2019-02-14 12:35:22 +08:00
|
|
|
if (is_repository_shallow(the_repository)) {
|
|
|
|
|
perform_reachability_traversal(&revs);
|
2018-10-24 23:56:12 +08:00
|
|
|
prune_shallow(show_only ? PRUNE_SHOW_ONLY : 0);
|
prune: lazily perform reachability traversal
The general strategy of "git prune" is to do a full reachability walk,
then for each loose object see if we found it in our walk. But if we
don't have any loose objects, we don't need to do the expensive walk in
the first place.
This patch postpones that walk until the first time we need to see its
results.
Note that this is really a specific case of a more general optimization,
which is that we could traverse only far enough to find the object under
consideration (i.e., stop the traversal when we find it, then pick up
again when asked about the next object, etc). That could save us in some
instances from having to do a full walk. But it's actually a bit tricky
to do with our traversal code, and you'd need to do a full walk anyway
if you have even a single unreachable object (which you generally do, if
any objects are actually left after running git-repack).
So in practice this lazy-load of the full walk catches one easy but
common case (i.e., you've just repacked via git-gc, and there's nothing
unreachable).
The perf script is fairly contrived, but it does show off the
improvement:
Test HEAD^ HEAD
-------------------------------------------------------------------------
5304.4: prune with no objects 3.66(3.60+0.05) 0.00(0.00+0.00) -100.0%
and would let us know if we accidentally regress this optimization.
Note also that we need to take special care with prune_shallow(), which
relies on us having performed the traversal. So this optimization can
only kick in for a non-shallow repository. Since this is easy to get
wrong and is not covered by existing tests, let's add an extra test to
t5304 that covers this case explicitly.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2019-02-14 12:35:22 +08:00
|
|
|
}
|
2013-12-05 21:02:54 +08:00
|
|
|
|
2022-04-14 04:01:36 +08:00
|
|
|
release_revisions(&revs);
|
2006-07-07 01:16:22 +08:00
|
|
|
return 0;
|
|
|
|
|
}
|
