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/.
Harald Welte laforge at gnumonks.orgDear Mike, it would be useful if you can send one patch against the git master of openbsc, that way I could apply your patch. The incremental patches are not really helpful because I need to find all of them on the list, look at them, figure out what has changed in which order, ... a simple git diff sha1_start..sha1_end (where sha1_start and sha1_end are the versions you can se in 'git log') is sufficient. On Tue, Oct 13, 2009 at 05:28:19PM +0100, Mike Haben wrote: > Mike Haben wrote: > >(Hopefully) last patch attached - now sends the correct op-code in > >response, works with all 6 phones I have tried. Interesting that > >5 out of 6 were happy with a completely different op-code and > >payload... It tells a lot about the protocol parser, and I'm not surprised. Be conservative in what you send and tolerant in what you accept is a very useful strategy in network protocols -- - Harald Welte <laforge at gnumonks.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)