clicking the <merge> button on the web view of the merge request to operate directly on the SourceForge repository also works OK
a subsequent "git pull" from my local copy correctly recognizes that the local/remote repositories are in agreement. (that surprised me a bit because I did not expect the hash values generated on the two machines to be identical, but they were. Is there no time- or machine- dependent component in the hash that git generates?)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
fetch/merge to my local copy works OK
clicking the <merge> button on the web view of the merge request to operate directly on the SourceForge repository also works OK
a subsequent "git pull" from my local copy correctly recognizes that the local/remote repositories are in agreement. (that surprised me a bit because I did not expect the hash values generated on the two machines to be identical, but they were. Is there no time- or machine- dependent component in the hash that git generates?)
I guess that is to be expected. Since the patches were on top of the master branch head that was only a fast-forward.