On Thu, Jun 07, 2007 at 04:32:35PM -0400, kurt_p_lloyd wrote: > One thing I was thinking might be useful would be a command to make > (just) my repository unavailable for 'fetch' or 'pull' from others, > temporarily. And then a command to make it available again, > after I finish things that could end up needing "database" surgery, > like maybe something that could result in having to do a git reset. > I was thinking maybe something like: > > $ git config maintenance true > .... do something that may end up needing "database" surgery > $ git config maintenance false You could probably do that with file permissions, but... > Just an idea. Of course, if something like this already exists .... > (I'd rather not shut down sshd, nor have to create a separate "public" > repository (for certain types of "projects" anyway).) ... why not? Having a separate public repository also allows you to do this and much more. And it should be cheap and easy--if you're worried about the space, clone with --shared or something. --b. - 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
