On Mon, 16 Feb 2009, Johannes Schindelin wrote:
On Sun, 15 Feb 2009, david@xxxxxxx wrote:
On Sun, 15 Feb 2009, Junio C Hamano wrote:
Thanks.
* git-push to update the checked out branch will be refused by default
Make "git push" into a repository to update the branch that is checked
out fail by default.
http://thread.gmane.org/gmane.comp.version-control.git/107758/focus=108007
If I understand this one, it will cause grief for quite a few people.
I have a public repository that I push to and then have a trigger that checks
out the current version, compiles it, publishes the compiled version, sends an
announcement, etc
So you have to set a config variable. Big deal.
Compared to that, the thousands of new Git users will no longer be bitten
by the "do not push to a non-bare repository" issue without a useful error
message.
Please, please, publicize that if there is somebody who is doing the same
as you (which I deem a dangerous workflow; I certainly do not use it
myself) that they will have to adjust their receive.denyCurrentBranch
variable.
since this repository isn't use for anything other than publishing for
public access, what's so dangerous about it?
what do you think that I should be doing instead?
David Lang
--
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
