I'd prefer to implement Daniel's proposition, when I get the time, if everyone agrees, that do another temporary change that would add more confusion.
> - Thomas Gazagnaire, 03/08/2015 10:30 - > >> FWIW this just happened to me, lost an hour and half banging my head on > >> the table (that may have helped with other things though). > > > > How about moving mixed mode to "path" instead of "git" (as I think > > someone suggested before)? > > > > i.e. > > > > "git pin -k path ..." (or just "git pin") will use mixed mode if possible > > "git pin -k git ..." uses the Git commit, ignoring the working tree Then it wouldn't be possible to ask for pure path pinning to a version-controlled directory anymore. > > To avoid ambiguity: `git pin -k mixed` maybe? > we could have a hack: (mixed => auto, and allow mixed mode | git => implicitely add #HEAD | other vcs => ...) But as I said above, I prefer to focus on a real improvement in the middle term.
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ opam-devel mailing list [email protected] http://lists.ocaml.org/listinfo/opam-devel
