From: Jeff King <peff@peff.net>
To: Bryan Turner <bturner@atlassian.com>
Cc: Jonathan Nieder <jrnieder@gmail.com>, Git Users <git@vger.kernel.org>
Subject: Re: http-protocol question
Date: Tue, 2 Dec 2014 00:52:29 -0500 [thread overview]
Message-ID: <20141202055228.GA2708@peff.net> (raw)
In-Reply-To: <CAGyf7-FDRS_zGQSFKhV8UGfN5GjGcyo0yCz8bcjEALYF3oj=Bg@mail.gmail.com>
On Tue, Dec 02, 2014 at 04:47:50PM +1100, Bryan Turner wrote:
> > There is a practical reason to care. Ref deletion will also delete the
> > reflog, leaving no trace of the reachability. Whereas a non-fast-forward
> > push could be resolved by looking in the reflog.
>
> A fair point. I had mistakenly thought that reflogs would survive the
> ref's deletion and be "pruned" as part of garbage collection, but a
> quick test shows that, as I'm sure you already know, that's not true.
I wish it worked that way. Unfortunately there are complications with
keeping the old reflogs in place, because they sometimes cause conflicts
with new refs being created (e.g., a reflog in ".git/logs/refs/heads/foo"
would prevent ".git/logs/refs/heads/foo/bar" from being created). I had
some patches long ago to try to keep a "reflog graveyard" around, but
they were quite invasive, and there were some corner cases that caused
weird errors.
Handling this sort of D/F conflict more gracefully is one of the things
I'd like to experiment with once we have pluggable ref backends (I think
we'll also disallow "foo/bar" if "foo" exists, but the storage could at
least keep the reflogs around).
-Peff
next prev parent reply other threads:[~2014-12-02 5:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-02 2:17 http-protocol question Bryan Turner
2014-12-02 3:34 ` Jonathan Nieder
2014-12-02 4:28 ` Bryan Turner
2014-12-02 4:29 ` Bryan Turner
2014-12-02 4:45 ` Jonathan Nieder
2014-12-02 5:04 ` Bryan Turner
2014-12-02 5:17 ` Jonathan Nieder
2014-12-02 5:30 ` Duy Nguyen
2014-12-02 5:37 ` Duy Nguyen
2014-12-02 5:33 ` Jeff King
2014-12-02 5:47 ` Bryan Turner
2014-12-02 5:52 ` Jeff King [this message]
2014-12-02 17:45 ` Junio C Hamano
2014-12-02 19:50 ` 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=20141202055228.GA2708@peff.net \
--to=peff@peff.net \
--cc=bturner@atlassian.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
/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.