From: Daniel W. <d.w...@sa...> - 2013-03-26 10:59:36
|
Hello, On 26/03/13 10:41, Tom Hacohen wrote: > On 26/03/13 10:32, Kim Woelders wrote: >> However, I have been adding (simple) tags for a number of release >> commits, but it looks like I'm not allowed to push them: >> $ git push --tags >> Total 0 (delta 0), reused 0 (delta 0) >> remote: C refs/tags/e16-1.0.10 e16/e16 kwo DENIED by fallthru >> remote: error: hook declined to update refs/tags/e16-1.0.10 >> remote: C refs/tags/e16-1.0.11 e16/e16 kwo DENIED by fallthru >> remote: error: hook declined to update refs/tags/e16-1.0.11 >> remote: C refs/tags/e16-1.0.12 e16/e16 kwo DENIED by fallthru >> remote: error: hook declined to update refs/tags/e16-1.0.12 >> To git+ssh://gi...@gi.../e16/e16.git >> ! [remote rejected] e16-1.0.10 -> e16-1.0.10 (hook declined) >> ! [remote rejected] e16-1.0.11 -> e16-1.0.11 (hook declined) >> ! [remote rejected] e16-1.0.12 -> e16-1.0.12 (hook declined) >> error: failed to push some refs to >> 'git+ssh://gi...@gi.../e16/e16.git' >> >> Is this on purpose? > Yes, the format for tags is: > v1.0.10 We decided on this to make all the repositories look alike and not have a chaos with some repos using one format and others using something completely different. Having said that I fear that we are sort of screwing with a workflow that you have been used to and using for a while now, which is definitely not what we intended! The question now is: How do we go forward? Would it be okay/easy for you to change the work flow? Do you have convincing arguments why our current work flow is flawed and we should change? Do you want us to leave your repositories the hell alone so you can do with it whatever you want? I would be strongly in favour of option 1, but then...I'm biased. Regards, Daniel |