On Tuesday 21 June 2011, Jonathan Nieder wrote: > Joey Hess wrote[1]: > > * git notes merge -s cat_sort_uniq > > > > Notes are stored in a tree using the object sha, which can be > > union merged, when the notes' format is a series of independant > > lines. > > > > [...] > > > > So I've written a prototype of a git-union-merge that could be used > > for all of these. It works like this: > > > > git union-merge foo origin/foo refs/heads/foo > > [...] > > If the prototype were self-contained, I would encourage you to submit > it for inclusion under contrib/ so it can evolve and eventually > graduate out of there. Cc-ing Johan (who has no doubt thought through > these things in the context of "git notes") in case he has thoughts on > it. Thanks for the CC. I must confess that my Haskell skills are exactly nil, but AFAICS the script depends on the filename as the only criteria to identify files that need a line-level merge. How does the script deal with renamed and copied files? If you depend on the filename only, this script simply will not work for notes. The notes tree reorganizes itself dynamically for optimum performance, and this affects how notes trees can be merged. E.g. given a note for object 01234567..., this note may exist as "01234567..." in one notes tree, while it may exist as "01/234567..." in a bigger notes tree, or even "01/23/4567..." in an even bigger notes tree. Even though the filenames differ, they all refer to the same note, and you cannot merge notes trees correctly without taking that fact into account. Furthermore, if you (union-)merge two notes trees that both have "01/234567...", the result does not necessarily belong in "01/234567...". It could be that the sum/union of the two notes trees have pushed the number of notes in the result so high that "01/23/4567..." is now a more optimal name for this note. ...Johan -- Johan Herland, <johan@xxxxxxxxxxx> www.herland.net -- 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