On Tue, Mar 03, 2009 at 02:57:15PM -0500, Jay Soffian wrote: > FWIW, I like this proposal. The only issue I have which I think simply > cannot be reconciled is this: it doesn't do anything to help a user > that expects "git push --init ssh://..." to "just work". (And here I'm > assuming push --init just calls init --remote under the covers.) The > reason is that such a user is probably just using the git supplied by > their vendor, and thus remote creation is likely disabled by default. > The best I can come up with is a different error message: > > "Sorry, remote repo creation not allowed. To enable it, blah blah blah" > > So at least the user has a clue that git can help them here, but there > are security reasons it does not do so by default. Yeah, the error messages should be more descriptive. Sites that have a web interface can even do: Sorry, remote repo creation must be down through the web interface. Please go to http://host/$user/create/$repo. where the URL can be customized based on the user and repo that made the request. Now we just need somebody who cares enough about this feature to work on it. ;) -Peff -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
