The stash makes use of git's reflog mechanism, but it is not a reflog
in the traditional sense. Each entry is a state that the user explicitly
requested git to remember. The stash is generally short-lived, but the
user probably expects that a stash will continue to exist until it is
explicitly deleted. So we should not expire stash entries.
Signed-off-by: Brandon Casey <casey@xxxxxxxxxxxxxxx>
---
builtin-gc.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/builtin-gc.c b/builtin-gc.c
index f5625bb..5cb74ec 100644
--- a/builtin-gc.c
+++ b/builtin-gc.c
@@ -30,7 +30,7 @@ static char *prune_expire = "2.weeks.ago";
#define MAX_ADD 10
static const char *argv_pack_refs[] = {"pack-refs", "--all", "--prune", NULL};
-static const char *argv_reflog[] = {"reflog", "expire", "--all", NULL};
+static const char *argv_reflog[] = {"reflog", "expire", "--all", "--exclude=refs/stash", NULL};
static const char *argv_repack[MAX_ADD] = {"repack", "-d", "-l", NULL};
static const char *argv_prune[] = {"prune", "--expire", NULL, NULL};
static const char *argv_rerere[] = {"rerere", "gc", NULL};
--
1.5.5.3
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
