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/.
Luca Bertoncello bertoncello at netzing.de-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am Wed, 23 Jun 2010 17:59:47 +0800 schrieb Holger Hans Peter Freyther <holger at freyther.de>: > On 06/23/2010 05:08 PM, Luca Bertoncello wrote: > > > Exact! :D > > The easiest is to use git bisect. > > git bisect start -- openbsc (to limit it to that subdir) > > git bisect good GOOD_REVISION (the sha1 not the stuff before the > hyphen) git bisect bad BAD_REVISION.. > > then repeat... > > $ make > $ test_it... > > and then either > $ git bisect good or git bisect bad... > > at the end git will show you the commit that introduced the problem... Hi, I don't know git. Could you please help me and say how can I get the two revision hashes? I just know the BSC version numbers. Thanks - -- _______________________________________________________________________ Luca Bertoncello Entwicklung Mail: bertoncello at netzing.de NETZING Solutions AG Tel.: 0351/41381 - 0 Kesselsdorfer Str. 216, 01169 Dresden Fax: 0351/41381 - 12 HRB 18926 / Ust.ID DE211326547 Mail: netzing.ag at netzing.de _______________________________________________________________________ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFMIfnDAXzltVKV/2wRAvXXAJ9QU3QCHkQyzlX1++n6/uA5Z1QEOACgwyZ0 sHU52E6cIua/69dIU+JsCxY= =hgNM -----END PGP SIGNATURE-----