> -----Original Message----- > From: Jan Waclawek [mailto:konf...@efton.sk] > Sent: Friday, September 18, 2009 3:41 PM > To: Ruddick Lawrence > Cc: Weddington, Eric; avr-libc-dev@nongnu.org > Subject: Re: [avr-libc-dev] Adding (some) Procyon > AVRlibfunctionalitytoavr-libc > > On Fri, 18 Sep 2009 13:45:47 -0700 > Ruddick Lawrence <rudd...@stanford.edu> wrote: > > > The confusion I was talking about with LibAVR was not with > the existing > > Procyon library, but with avr-libc. Of course that only > becomes a problem if > > they are indeed separate projects, which brings me to my > second point... > > Want some crazy (but google-safe) names? > > yalfa (yet another library for avr)
Personally I really hate anything with "yet another" in the name. And point to the legions of AVR libraries out that that warrants that this is "yet another" library. > lidr, or avr-lidr (from library & drivers) > bonbon (not really google-safe, but certainly good ;-) ) > > Count me into the "will contribute chaotically" group, unless > you insist on the CVS stuff, which I am not willing to learn > to use properly (I guess there might be more of us with this > attitude). CVS is not that hard to learn, and it's a good skill to have. Here's the reference that I use: http://cvsbook.red-bean.com/cvsbook.html Once you know CVS, then Subversion is not that hard to learn. _______________________________________________ AVR-libc-dev mailing list AVR-libc-dev@nongnu.org http://lists.nongnu.org/mailman/listinfo/avr-libc-dev
