From: "Shawn O. Pearce" <spearce@spearce.org>
To: Jeff King <peff@peff.net>
Cc: Junio C Hamano <gitster@pobox.com>,
Nguyen Thai Ngoc Duy <pclouds@gmail.com>,
git@vger.kernel.org
Subject: Re: [PATCH] logging branch deletion to help recovering from mistakes
Date: Tue, 7 Dec 2010 10:23:42 -0800 [thread overview]
Message-ID: <20101207182342.GA3725@spearce.org> (raw)
In-Reply-To: <20101207182040.GA26770@sigill.intra.peff.net>
Jeff King <peff@peff.net> wrote:
> On Tue, Dec 07, 2010 at 10:14:19AM -0800, Shawn O. Pearce wrote:
>
> > Per check-ref-format, ref names cannot contain two dots. We could
> > archive ref logs by renaming them, $GIT_DIR/logs/refs/heads/foo
> > becomes $GIT_DIR/logs/refs/heads/foo..deleted-1. If foo is created
> > and deleted again, it becomes foo..deleted-2.
...
> > A different approach might be to have $GIT_DIR/logs/refs/REF_ATTIC,
>
> That seems a lot less efficient, as we have to linearly search all of
> REF_ATTIC to get:
>
> 1. the reflog for one deleted branch
>
> 2. the list of deleted branches
>
> Neither of those is probably particularly performance critical, but it
> just seems like keeping the logs in files indexed by the original ref
> names is a more natural fit.
Yea, I'm leaning more towards the foo..deleted-n idea too, for the
same reasons. It also makes it easier to GC a deleted branch's
reflog, we can examine the last record's timestamp in a reasonable
time bound and unlink the log if its really freaking old.
--
Shawn.
next prev parent reply other threads:[~2010-12-07 18:23 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-06 21:16 [PATCH] logging branch deletion to help recovering from mistakes Junio C Hamano
2010-12-06 21:55 ` Štěpán Němec
2010-12-06 23:14 ` Andreas Schwab
2010-12-07 1:18 ` Nguyen Thai Ngoc Duy
2010-12-07 6:28 ` Junio C Hamano
2010-12-07 11:37 ` Nguyen Thai Ngoc Duy
2010-12-07 15:25 ` Michael J Gruber
2010-12-07 16:25 ` Nguyen Thai Ngoc Duy
2010-12-07 16:22 ` Jakub Narebski
2010-12-07 16:26 ` Nguyen Thai Ngoc Duy
2010-12-07 17:06 ` Jeff King
2010-12-07 18:14 ` Shawn Pearce
2010-12-07 18:20 ` Jeff King
2010-12-07 18:23 ` Shawn O. Pearce [this message]
2010-12-07 18:35 ` Jeff King
2010-12-07 18:37 ` Shawn O. Pearce
2010-12-07 18:39 ` Jeff King
2010-12-07 18:41 ` Shawn O. Pearce
2010-12-07 19:21 ` Junio C Hamano
2010-12-07 19:38 ` Jeff King
2010-12-07 16:23 ` Casey Dahlin
2010-12-07 17:45 ` Jonathan Nieder
2010-12-07 17:54 ` Casey Dahlin
2010-12-07 18:02 ` Jonathan Nieder
2010-12-07 18:26 ` Casey Dahlin
2010-12-07 20:25 ` Junio C Hamano
2010-12-07 20:55 ` Jonathan Nieder
2010-12-07 18:12 ` Jeff King
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20101207182342.GA3725@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=pclouds@gmail.com \
--cc=peff@peff.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.