Re: [PATCH] Switch receive.denyCurrentBranch to "refuse"
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Feb 2, 2009, 08:32 UTC
- Message-ID
- <7v1vuhkzmp.fsf@gitster.siamese.dyndns.org>
- In-Reply-To
- <1233558035.20131.72.camel@maia.lan>
Sam Vilain <sam@vilain.net> writes:
> The other affects > a small number of users who are doing something which is labeled in many > places as a bad thing to want to do.
Sorry, but I do not agree with this.
What is bad is to push into a repository that is used for editing. That is labelled as a bad thing to want to do.
It is often the easiest to push and then run "reset --hard" (perhaps from the post-update script) to propagate your change to a repository that is not usually used for editing. E.g. that has always been the way I update my private repository at k.org that I use for final testing before pushing out the results that I built and tested on my personal machine. People who have live web pages served from a checkout do that, too. It is not a bad thing to do at all, and you can find many instructions with google without spending a lot of time to do exactly that.
http://kerneltrap.org/mailarchive/git/2008/7/1/2315924
http://utsl.gen.nz/git/post-update
http://groups.google.com/group/sl-ugr/browse_thread/thread/04e4c4bd6ce174af