On Sun, Jul 29, 2012 at 7:43 PM, Fredrik Gustafsson <iv...@iveqy.com> wrote: > On Sun, Jul 29, 2012 at 04:07:13PM +0530, Sitaram Chamarty wrote: >> On Sun, Jul 29, 2012 at 3:11 AM, Fredrik Gustafsson <iv...@iveqy.com> wrote: >> > Hi, >> > sometimes git communicates with something that's not git on the other >> > side (gitolite and github for example). >> > >> > Sometimes the server wants to communicate directly to the git user. >> > >> > git isn't really designed for this. gitolite solves this by do user >> > interaction on STDERR instead. The bad thing about this is that it can >> > only be one-direction communication, for example error messages. >> > >> > If git would allow for the user to interact direct with the server, a >> > lot of cool and and userfriendly features could be developed. >> > >> > For example: >> > gitolite has something called wild repos. The management is >> > cumbersome and if you misspell when you clone a repo you might instead >> > create a new repo. >> >> For the record, although it cannot do the yes/no part, if you want to >> disable auto-creation on a fetch/clone (read operation) it's trivial >> to add a "PRE_CREATE" trigger to do that. > > Thanks, however I think auto-creation is a great feature for some cases > and I think there can be even more useable functions if we could get > user interaction.
For the record, I don't think I agree. There's a place to create a human-conversation, and there's a place not to. If you want a dialog with the server, there should be *other* commands that do that, instead of overloading git's own protocol. Since you mentioned gitolite, consider copying the fork command (src/commands/fork) and munging the code into an explicit wild repo create. -- 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