Cloned repository changes

@PB

How to sign, if somebody has a change in his cloned repository, which you should merge into yours? (i.e. how to do pull requests for such, because bitbucket doesn't allow me to do so)
I have to merge every change of yours lately, because mine changes are not merged back...
Or should we treat for example the language changes otherwise? I mean should I always post the corrected language file instead of pushing it to my repo?

FDR wrote: @PB

How to sign, if somebody has a change in his cloned repository, which you should merge into yours? (i.e. how to do pull requests for such, because bitbucket doesn't allow me to do so)
I have to merge every change of yours lately, because mine changes are not merged back...
Or should we treat for example the language changes otherwise? I mean should I always post the corrected language file instead of pushing it to my repo?

The easiest way to do it is to fork my repository from bitbucket. either discard your current repo, or create another with a different name.
in bitbucket, go to my repo, and then select 'fork'
you can now check out your new repository and make changes and check in as usual (you probably want to copy the .hgrc file from your current repo into the new one to make syncing easier)

Anyhow, now you can generate pull requests from bitbucket

OK, I'll give it a try...

If you could solve the gcc version problem too...

Hopefully it will work for you now.

Yep, it compiles now...

I was able to send a pull request too...
Will it do this way?

FDR wrote: I was able to send a pull request too...
Will it do this way?

Yes that worked quite well. I can just click a button to accept your pull.