On Sat, 20 Jul 2013, Andy Bradford wrote:
I've been working on a simple fossil command that will integrate with SSH accounts where SSH keys are in use and wonder if there is a formal process for coming up with new subcommand names? Here is what I have at the moment:$ fossil help gate Usage: fossil gate ?FILENAME? fossil gate ?FILENAME? Scans filename for the requested fossil path found in the SSH_ORIGINAL_COMMAND environment variable and runs fossil http path if found. If filename is not present, just run fossil http with the requested path and the operating system will impose restrictions.
Regardless of whether this is a good idea or not, please do not call it "fossil gate". Please give it a name that alerts the user to the fact that it's very closely tied to ssh. Also, given the intended usage, I think it should fail closed, not fail open. --apb (Alan Barrett) _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
