Johan Herland <johan@xxxxxxxxxxx> writes: > On Wed, Jul 29, 2015 at 4:00 AM, Junio C Hamano <gitster@xxxxxxxxx> wrote: > >> So doing the absolute minimum, leaving the "now what can we do to >> improve notes-merge process?" outside the scope of the topic. > > That's exactly what I was also trying to do: David's topic should not > have to deal with NOTES_MERGE_* at all. Simply leave it all as > something that belongs in $GIT_COMMON_DIR, and let's solve concurrent > unrelated notes merges as a wholly independent, separate topic. Here, it perhaps is showing that you are unfamiliar with the linked worktree topic. Things directly under .git/, like HEAD, MERGE_HEAD, etc., are per worktree (i.e. not shared across working trees). You have to work to make them shared, i.e. per repo. David's earlier one downcased them while still keeing them directly under .git/ but I think it is ugly and in general a wrong way to mark what is shared and what is per worktree. E.g. index is not shared, even though the name is all lowercase. You will be updating that mechanism when you truly make the notes-merge a per refs/notes/* ref thing (not per repo, not per worktree). Perhaps you will use refs/notes-merge/$foo that is shared across worktrees as the replacement for NOTES_MERGE_REF that currently is used to merge into refs/notes/$foo, or something like that, to pursue your "per ref" goal. At that point, NOTES_MERGE_REF based design needs to be scrapped anyway; it should not matter if NOTES_MERGE_REF is per worktree (not shared) or per repo (shared) in the meantime. Doing absolute minimum means that $GIT_DIR/NOTES_MERGE_REF should be left per worktree, like MERGE_HEAD, etc., without doing anything like downcasing or moving it under refs/notes-merge/ (which I think is a better way to make it shared, if we wanted to), which is additional special casing that will be a wasted effort that would not matter in the end result. -- 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