From: Junio C Hamano <gitster@pobox•com>
To: Michael Haggerty <mhagger@alum•mit.edu>
Cc: Lars Schneider <larsxschneider@gmail•com>,
Git Mailing List <git@vger•kernel.org>,
Luke Diamand <luke@diamand•org>,
novalis@novalis•org
Subject: Re: What's cooking in git.git (Jun 2016, #05; Thu, 16)
Date: Mon, 27 Jun 2016 09:29:46 -0700 [thread overview]
Message-ID: <xmqqinwubnnp.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <576B9081.3020405@alum.mit.edu> (Michael Haggerty's message of "Thu, 23 Jun 2016 09:32:17 +0200")
Michael Haggerty <mhagger@alum•mit.edu> writes:
> I'd like to request that the change for the p4 temprefs be made in two
> steps:
>
> 1. Write references to `refs/git-p4-tmp` or whatever, without
> worrying about making them per-worktree.
>
> 2. Carve out a per-worktree namespace, bikeshed about its name and
> semantics, make sure it works correctly, then finally move the
> p4 temporary references and eventually the bisect references there.
Hasn't 2. already happened long time ago? I thought that the
direction was that bisect will have to be grandfathered to stay
there, and new things would hang beneath a single per-worktree
hierarchy.
I would have expected that your 1. would be a request to use
refs/worktrees/git-p4-tmp.
... goes and looks ...
Ahh, I did misremember the discussions.
http://thread.gmane.org/gmane.comp.version-control.git/276628
http://thread.gmane.org/gmane.comp.version-control.git/276960/focus=276963
It appears that in the latter, a more generic refs/worktrees/ was
somehow postponed, and only bisect was made per-worktree to fix the
immediate breakage.
> The reason is that step 1 is low-risk, could be made quickly, and is
> enough to unblock mh/split-under-lock and the other patch series that
> depend on it. Step 2, on the other hand, could take quite a while, and
> its implementation might benefit from changes to reference handling that
> are in the pipeline (e.g., perhaps the horrible hack can be dispensed
> with). Meanwhile, as far as I understand these references are transient,
> so there are no backwards-compatibility considerations that make
> renaming them twice more cumbersome than renaming them once.
next prev parent reply other threads:[~2016-06-27 16:29 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-17 3:20 What's cooking in git.git (Jun 2016, #05; Thu, 16) Junio C Hamano
2016-06-17 13:25 ` Pranit Bauva
2016-06-17 17:55 ` Vasco Almeida
2016-06-17 22:05 ` Lars Schneider
2016-06-17 22:17 ` Junio C Hamano
2016-06-18 17:09 ` Michael Haggerty
2016-06-19 7:59 ` Michael Haggerty
2016-06-19 15:04 ` Lars Schneider
2016-06-19 16:11 ` Lars Schneider
2016-06-19 18:13 ` Junio C Hamano
2016-06-19 18:49 ` Lars Schneider
2016-06-19 18:53 ` Lars Schneider
2016-06-19 18:09 ` Junio C Hamano
2016-06-19 23:51 ` Junio C Hamano
2016-06-20 7:57 ` Lars Schneider
2016-06-23 7:32 ` Michael Haggerty
2016-06-27 7:09 ` Lars Schneider
2016-06-27 16:29 ` Junio C Hamano [this message]
2016-06-28 9:23 ` Michael Haggerty
2016-06-28 17:44 ` Junio C Hamano
2016-06-18 4:18 ` Michael Haggerty
2016-06-18 18:20 ` Junio C Hamano
2016-06-19 8:15 ` Michael Haggerty
2016-06-19 18:07 ` Junio C Hamano
2016-06-20 6:06 ` Torsten Bögershausen
2016-06-20 20:06 ` Junio C Hamano
2016-06-22 21:09 ` Joey Hess
2016-06-23 13:13 ` Torsten Bögershausen
2016-07-12 22:20 ` Joey Hess
2016-07-14 2:09 ` Torsten Bögershausen
2016-07-14 18:17 ` Junio C Hamano
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=xmqqinwubnnp.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=larsxschneider@gmail$(echo .)com \
--cc=luke@diamand$(echo .)org \
--cc=mhagger@alum$(echo .)mit.edu \
--cc=novalis@novalis$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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