From: Jeff King <peff@peff.net>
To: Mike Hommey <mh@glandium.org>
Cc: Karl Moskowski <kmoskowski@me.com>,
Michael Haggerty <mhagger@alum.mit.edu>,
git@vger.kernel.org
Subject: Re: Bug: Branch Deletion Doesn't Clean Up
Date: Thu, 4 Feb 2016 03:29:11 -0500 [thread overview]
Message-ID: <20160204082911.GA23479@sigill.intra.peff.net> (raw)
In-Reply-To: <20160204082613.GA14076@glandium.org>
On Thu, Feb 04, 2016 at 05:26:13PM +0900, Mike Hommey wrote:
> > There are a few reasons not to:
> >
> > - it breaks backwards compatibility (unless we continue to create the
> > directory in order to put the dot-lock in it, but then I don't think
> > we've gained anything)
>
> Is that the kind of backwards compatibility that matters, though? I
> mean, I won't claim to know all the internals of how refs are used, but
> you sound like the theoretical incompatibility would be two different
> versions of git racing for update-ref on the same local repository.
Yes, that's true. It's a lesser breakage than "you cannot go back to the
old version at all".
-Peff
prev parent reply other threads:[~2016-02-04 8:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-07 19:24 Bug: Branch Deletion Doesn't Clean Up Karl Moskowski
2016-02-04 7:54 ` Jeff King
2016-02-04 7:55 ` Jeff King
2016-02-04 8:12 ` Mike Hommey
2016-02-04 8:17 ` Jeff King
2016-02-04 8:26 ` Mike Hommey
2016-02-04 8:29 ` Jeff King [this message]
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=20160204082911.GA23479@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=kmoskowski@me.com \
--cc=mh@glandium.org \
--cc=mhagger@alum.mit.edu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).