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/tetra@lists.osmocom.org/.
n0p [Luis Bernal] lbernal at gmail.comI think you'll have to send a patch to this list to have it reviewed. 2017-01-13 12:37 GMT+01:00 Jannik Jürgens <jjuergens at seemoo.tu-darmstadt.de> : > Dear Osmocom Community, > > I currently writing my masterthesis about TETRA. For this, I am > currently writing my master thesis on TETRA. For this the support of DMO > is necessary. Another student had already implemented a rudimentary DMO > receiver (based on the Osmocom code) in his thesis, which I now develop > further. I would like to add this code to the Osmocom project as a new > branch so that other people can participate. > > I was unsure, based on which branch I should develop the code, but I > decide for the laforge / sq5bpf-rebase-20161218 branch, because this is > most useful for my purpose. I hope this is okay and doesn't lead to > chaos. When trying to create a new branch and commit this, however I get > an error message: > > $ Git push origin jj / dmo > Error: no DAV locking support at https://git.osmocom.org/osmo-tetra/ > Fatal: git-http-push failed Error: Error sending some references to > 'https://git.osmocom.org/osmo-tetra' > > Unfortunately, I have not found instructions, who is at Osmocom allowed > to commit code or how the process works. Can you help me with this or > send me a link, where I find the appropriate information? > > Best regards, > Jannik > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.osmocom.org/pipermail/tetra/attachments/20170113/9ecdc130/attachment.htm>