Johan Herland <jo...@herland.net> writes: > Alternatively (or additionally), for issue (2), we could add a > --disable-ref-safety option to 'git notes', to explicitly disable the > safety checks for "experimental" use.
I actually would rather prefer to see a proper plumbing use supported, either by a new "git notes-plumb" subcommand or "git notes --<some option>" that gives the scriptors a stable interface to the low-level machinery without enforcing any Policy that belongs to the Porcelain layer. At the very least, the plumbing should: - disable anything that introduces potential ambiguity, e.g. DWIMs done by expand_notes_ref(), but not limited to it. - lift any restrictions based on policy, e.g. "where can notes trees live" (again, but not limited to this). -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
