Hi Ævar, On Fri, 16 Mar 2018, Ævar Arnfjörð Bjarmason wrote: > > On Fri, Mar 16 2018, Johannes Schindelin jotted: > > > On Thu, 15 Mar 2018, Linus Torvalds wrote: > > > >> We do end up still using the dashed form for certain things, but they > >> are already special-cased (ie things like "git-receive-pack" and > >> "git-shell" that very much get executed directly, and for fundamental > >> reasons). > > > > Please do elaborate. > > If you were to set set "/bin/git shell" in /etc/password it would not do > the right thing as far as I know. Is that a shell name with a space in > it, or the "shell" argument to /bin/git? True. And `git-shell` is not a builtin, so it does not even matter with regards to this discussion. > There's also the fully dashed forms of stuff like git-receive-pack is > part of the over-ssh convention, i.e.: > > ssh <host> git-upload-pack ... Even if upload-pack is not a builtin (and thus still has to be its own executable), receive-pack *is*, so this does affect our current discussion. This is a real problem. And it is our own darned fault because we let an implementation detail bleed into a protocol. We could have designed that a lot better. Of course we should fix this, though. There is literally no good reason that I can think of why we should not change this to `ssh <host> git upload-pack ...` (of course with an insanely long deprecation period). Ciao, Dscho
