This is merely a historical archive of years 2008-2021, before the migration to mailman3.
A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/OpenBSC@lists.osmocom.org/.
Neels Hofmeyr nhofmeyr at sysmocom.deSo after some blood boiling to my head (sorry about that), I hit rebase, waited for jenkins and then the change could be merged. Next I have to hit rebase on all following commits submitted from the same branch. It would be nice if Gerrit could have the series of branch commits in-a-row and rebase them together in one flush, especially since they depend on each other. Also I find it hard to see the intended sequence of branch commits. The sorting of patches changes by updating the patch submission, so the branch commits in the Gerrit UI are potentially re-ordered regularly. Would it make sense to locally merge the branch to master and submit the resulting merge-commit for review instead? Then Gerrit would treat it as a single patch, yet the merge commit could contain any number of "sub" commits? It would also be nice if Gerrit didn't complain about merge conflicts that are in fact no merge conflicts -- I'm stumped on that topic. Any help would be appreciated. Sorry again and thanks for any hints! ~Neels -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: Digital signature URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20160601/6587d5d7/attachment.bin>