Otoh, up to date and working examples make the library much more accessible for new users and is also useful for experienced folks too. Having them in the main repository helps remind developers to maintain them rather than having them languish in another repo. If you don't want to build the examples every time this is easily fixed with a Makefile target.
That said I'm not particularly advocating changing back and a git submodule is perhaps a good compromise. On 11 Jul 2013, at 10:21, Michael Smith <[email protected]> wrote: > > On Jul 11, 2013, at 8:19 AM, Pavol Rusnak <[email protected]> wrote: > >> I would like to ask why exactly were examples split into a separate >> libopencm3-examples repository. > > Probably because checking lots of (often broken) examples when all you want > is the library is *really*annoying*. > > = Mike > > > ------------------------------------------------------------------------------ > See everything from the browser to the database with AppDynamics > Get end-to-end visibility with application monitoring from AppDynamics > Isolate bottlenecks and diagnose root cause in seconds. > Start your free trial of AppDynamics Pro today! > http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk > _______________________________________________ > libopencm3-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/libopencm3-devel ------------------------------------------------------------------------------ See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk _______________________________________________ libopencm3-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libopencm3-devel
