SourceForge works well enough, so no, I don't have plans to move mspgcc to github. If you or somebody wants to initiate a github presence, feel free to do so; I could pull changes from there just as easily as elsewhere.
Peter On Mon, Dec 5, 2011 at 4:16 PM, Sergio Campamá <scamp...@ing.puc.cl> wrote: > Hey Peter, thanks for the great work! > > If I may ask, are you planning on (or thought about) moving the code over to > github sometime? I strongly believe that github is a better open source > platform than source forge, and since you already use git for version > control, it would take less than 5 minutes to set up the mspgcc account… > Maybe over there mspgcc could receive more attention and attract more > collaborators… This is just my humble opinion… > > Best regards, > --------------------------------------- > Sergio Campamá > sergiocamp...@gmail.com > > > > > On Dec 5, 2011, at 6:29 PM, Peter Bigot wrote: > >> There is a new suite of mspgcc patches available as mspgcc 20111205, >> available as a bundle at >> https://sourceforge.net/projects/mspgcc/files/mspgcc/. All components >> have been updated: binutils, gcc, gdb, msp430-libc, msp430mcu. This >> release is intended to be the first of a series of releases. Expect >> there to be new features added, old features removed, and interface >> changes over the course of the evolution. >> >> Since this path is likely to introduce temporary instabilities, I have >> intentionally prepared these patches to be based on the previous >> upstream releases (gcc 4.6.1, binutils 2.21.1a, gdb 7.2a) rather than >> the most recent upstream releases, to avoid confusion when the LTS >> release finally comes out: it will be based on the latest upstream >> releases available at that time. Since this is a development >> release, not a long-term-support (LTS) release, I will not be >> preparing standalone patches for reported problems. Instead, problems >> will be fixed in the git repository, and made available in subsequent >> development releases. LTS-20110716 will continue to be supported as a >> stable development platform until the next LTS release. >> >> All changes should correspond to an item in the mspgcc tracker at >> https://sourceforge.net/tracker/?group_id=42303&atid=432701. As I >> don't have much time available to document the changes outside of the >> source code and the tracker, I've stubbed out a wiki page at >> https://sourceforge.net/apps/mediawiki/mspgcc/index.php?title=Gcc46:Changes >> and would ask that, as you run across new stuff that's unexpected, you >> update that page. Edit privileges for the wiki can be obtained by >> following the process described on its front page at >> https://sourceforge.net/apps/mediawiki/mspgcc/index.php?title=MSPGCC_Wiki. >> >> Report any bugs you find on the tracker at >> https://sourceforge.net/tracker/?group_id=42303&atid=432701. >> >> Peter >> >> ------------------------------------------------------------------------------ >> All the data continuously generated in your IT infrastructure >> contains a definitive record of customers, application performance, >> security threats, fraudulent activity, and more. Splunk takes this >> data and makes sense of it. IT sense. And common sense. >> http://p.sf.net/sfu/splunk-novd2d >> _______________________________________________ >> Mspgcc-users mailing list >> Mspgcc-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/mspgcc-users > ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ Mspgcc-users mailing list Mspgcc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mspgcc-users
