We have notes merge support since a couple of releases now, but no real example in the docs of how best to use that. That is, no suggested mapping of remote notes, let alone automatic setup of refspecs at clone time. Trying to setup such refspecs, I find myself puzzled: * if I store remote notes under refs/notes (eg. refs/notes/*:refs/notes/origin/* as fetch refspec), then a refs/notes/*:refs/notes/origin/* push refspec will include refs/notes/origin/*, which we obviously don't want * if I store them outside of refs/notes (eg. refs/notes/*:refs/remote-notes/origin/* ), then "git notes" silently ignores them: no output nor any error message from "notes list" or "notes merge". Do we really want to "git notes" to ignore everything not in refs/notes/ ? I can think of 2 possibilities out of this situation: * remove that limitation * decide on a naming convention for remote notes, and teach "git notes" not to ignore it A (minor) problem with the second possibility is that this naming convention could evolve, eg. if we end up with something like was proposed in [1] for 1.8.0. Is there any real drawback with the first suggestion ? [1] http://marc.info/?l=git&m=129661334011986&w=4 -- Yann Dirson - Bertin Technologies -- 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