Well ... you have pretty much exhausted
my Git knowledge. Might have to get web master help.
But, I can suggest one other thing.
The way you describe it ... you "renamed your branch" .... sounds
like there might be some "history" there, that has a permeant
branch name? You might try "starting fresh" with one test file,
and if that works, copy others there.
Oh, wait ... I just looked on file system,
and looks like you are set up to do "Gerrit only" commits? I
think I did hear for that case, you do have to open a bug and ask web master
for help creating branches OR ... ask a Gerrit expert ... might be possible,
but I'm not that familiar with Gerrit.
discussions for paho project <paho-dev@xxxxxxxxxxx>,
02/01/2014 11:01 AM
Creating a new branch in git
that makes sense - although it isn't working for me having
renamed my branch 'noleary/develop':
(noleary/develop)$ git push origin noleary/develop
Counting objects: 26, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (20/20), done.
Writing objects: 100% (22/22), 27.69 KiB, done.
Total 22 (delta 7), reused 0 (delta 0)
error: insufficient permission for adding an object to
repository database ./objects
On 1 February 2014 15:13, David M Williams <david_williams@xxxxxxxxxx>
By policy, most repositories are set
up so it takes special action or web master assistance to create a new
"permeant" branch ... BUT, any committer can create a new "topic
branch" ... the format of the name just needs to be committerId/topic
... so, perhaps "nick/develop" will work for you? (The reason
for this is that "permeant branches" should never be deleted,
hence it is made "harder" to create them ... whereas if you create
a topic branch with your committer ID as part of the name, then the system
will not only allow you to create it, but you can delete it later).
back to the point where the .js file in git can actually be used without
running it through a maven build. This involved adding a very small wrapper
for the node-based tests to use so the client can still use the browser-specific
version (30Kb) as well as the original one (76kb).
I wanted to push this to a new branch (nick-develop) so that anyone with
an interest could have a look to make sure we're happy for it to go into
the main develop branch. However, when I try to push the new branch, I'm
told I don't have the right permissions:
error: insufficient permission for adding an object to repository
Does creating a new branch really need more permissions than I have as
a committer? If so, what is the expected work flow for this sort
of thing? (I suspect I'm too used to the github work flow where this is