[leaf-devel] IdeaTorrent
Everyone, Feel free to add your ideas. https://sourceforge.net/apps/ideatorrent/leaf/ -- Mike Noyes mhnoyes at users.sourceforge.net http://sourceforge.net/users/mhnoyes/ SF.net Projects: leaf, sourceforge/sitedocs -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
[leaf-devel] Mailing Lists
Everyone, Are there any objections to deleting the following mailing lists: leaf-announce, leaf-auto, leaf-hardware, leaf-wisp-dist This will leave: leaf-cvs-commits (rename to leaf-commits, or delete in favor of laconica w/git), leaf-devel, leaf-user -- Mike Noyes mhnoyes at users.sourceforge.net http://sourceforge.net/users/mhnoyes/ SF.net Projects: leaf, sourceforge/sitedocs -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] Mailing Lists
Martin, I'm willing to resume my duties as list manager. On Tue, 2010-04-06 at 09:38 -0700, Mike Noyes wrote: Everyone, Are there any objections to deleting the following mailing lists: leaf-announce, leaf-auto, leaf-hardware, leaf-wisp-dist This will leave: leaf-cvs-commits (rename to leaf-commits, or delete in favor of laconica w/git), leaf-devel, leaf-user -- Mike Noyes mhnoyes at users.sourceforge.net http://sourceforge.net/users/mhnoyes/ SF.net Projects: leaf, sourceforge/sitedocs -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] Mailing Lists
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 4/6/2010 11:38 AM, Mike Noyes wrote: Everyone, Are there any objections to deleting the following mailing lists: leaf-announce, leaf-auto, leaf-hardware, leaf-wisp-dist This will leave: leaf-cvs-commits (rename to leaf-commits, or delete in favor of laconica w/git), leaf-devel, leaf-user No objections here. Just -devel, -user, and -commits seems like plenty with the limited traffic these days. - -- Charles Steinkuehler char...@steinkuehler.net -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iD8DBQFLu2taLywbqEHdNFwRAhvTAKCj8y8GsXytG6TrY9NiFjJETbV/gACfb1j3 7D8ESGCjQPgQrdqKaEfK94Q= =NA5R -END PGP SIGNATURE- -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] Mailing Lists
Hi Mike, Are there any objections to deleting the following mailing lists: leaf-announce, leaf-auto, leaf-hardware, leaf-wisp-dist No objections at all - they've done nothing but receive spam for quite a while now. leaf-cvs-commits (rename to leaf-commits, or delete in favor of laconica w/git) how about if we wait until somebody has actually done the work of (or is actively working on) migrating CVS, plus all the support-scripts in buildtool and for the packages page and changelog on the homepage, before we start renaming mailing lists. It would seem a bit silly if we ended up with everything still in CVS (because nobody actually did a migration, or the migration was never finished) but have a commits-list that suggests otherwise. Just my 2 cents Martin -- You think that's tough? Try herding cats! -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] Mailing Lists
Hi Mike, I'm willing to resume my duties as list manager. feel free to do so if you'd like to. Due to the fact that the lists have been _very_ low traffic lately (apart from the spam that's automatically discarded), it's not been a burden - but if you'd like to take care of the lists again, that's ok with me. Martin -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] Mailing Lists
On Tue, 2010-04-06 at 19:21 +0200, Martin Hejl wrote: Hi Mike, Are there any objections to deleting the following mailing lists: leaf-announce, leaf-auto, leaf-hardware, leaf-wisp-dist No objections at all - they've done nothing but receive spam for quite a while now. Martin, Done. leaf-cvs-commits (rename to leaf-commits, or delete in favor of laconica w/git) how about if we wait until somebody has actually done the work of (or is actively working on) migrating CVS, plus all the support-scripts in buildtool and for the packages page and changelog on the homepage, before we start renaming mailing lists. Agreed. I have to look into export and import to git first. The only things I want to migrate are docs, bering-uclibc, and the unnamed one. Planned archival of cvs in the frs for historical use. It would seem a bit silly if we ended up with everything still in CVS (because nobody actually did a migration, or the migration was never finished) but have a commits-list that suggests otherwise. Agreed. -- Mike Noyes mhnoyes at users.sourceforge.net http://sourceforge.net/users/mhnoyes/ SF.net Projects: leaf, sourceforge/sitedocs -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] Mailing Lists
On Tue, 2010-04-06 at 19:39 +0200, Martin Hejl wrote: Hi Mike, I'm willing to resume my duties as list manager. feel free to do so if you'd like to. Due to the fact that the lists have been _very_ low traffic lately (apart from the spam that's automatically discarded), it's not been a burden - but if you'd like to take care of the lists again, that's ok with me. Martin, I'll take care of the changes today. Thank you for managing our lists. I greatly appreciate it. -- Mike Noyes mhnoyes at users.sourceforge.net http://sourceforge.net/users/mhnoyes/ SF.net Projects: leaf, sourceforge/sitedocs -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] Mailing Lists
On Tue, 2010-04-06 at 10:48 -0700, Mike Noyes wrote: On Tue, 2010-04-06 at 19:39 +0200, Martin Hejl wrote: Hi Mike, I'm willing to resume my duties as list manager. feel free to do so if you'd like to. Due to the fact that the lists have been _very_ low traffic lately (apart from the spam that's automatically discarded), it's not been a burden - but if you'd like to take care of the lists again, that's ok with me. Martin, I'll take care of the changes today. Thank you for managing our lists. I greatly appreciate it. Martin, Done. -- Mike Noyes mhnoyes at users.sourceforge.net http://sourceforge.net/users/mhnoyes/ SF.net Projects: leaf, sourceforge/sitedocs -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] Mailing Lists
On Tue, 2010-04-06 at 12:11 -0500, Charles Steinkuehler wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 4/6/2010 11:38 AM, Mike Noyes wrote: Everyone, Are there any objections to deleting the following mailing lists: leaf-announce, leaf-auto, leaf-hardware, leaf-wisp-dist This will leave: leaf-cvs-commits (rename to leaf-commits, or delete in favor of laconica w/git), leaf-devel, leaf-user No objections here. Just -devel, -user, and -commits seems like plenty with the limited traffic these days. Charles, Done, and thanks for the input. -- Mike Noyes mhnoyes at users.sourceforge.net http://sourceforge.net/users/mhnoyes/ SF.net Projects: leaf, sourceforge/sitedocs -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
[leaf-devel] Buildtool
Martin, What assistance will help with 'buildtool' conversion from cvs to git? http://leaf.cvs.sourceforge.net/viewvc/leaf/src/bering-uclibc/buildtool/ Everyone, This task is the main thing holding up a move to git. -- Mike Noyes mhnoyes at users.sourceforge.net http://sourceforge.net/users/mhnoyes/ SF.net Projects: leaf, sourceforge/sitedocs -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
[leaf-devel] The UnNamed One
Everyone, How about one of these straits: Bass, Bonifacio, Bosporus, Cook, Denmark, Dover, Georgia, Gibraltar, Hormuz, Hudson, Kara, Kerch, Korea, La Perouse, Laptev, Luzon, Malacca, Magellan, Matochkin, Menai, Messina, Otranto, Sannikov, Sicily, Taiwan, Tatar, or Vilkitshogo. -- Mike Noyes mhnoyes at users.sourceforge.net http://sourceforge.net/users/mhnoyes/ SF.net Projects: leaf, sourceforge/sitedocs -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] Buildtool
Hi Mike, What assistance will help with 'buildtool' conversion from cvs to git? http://leaf.cvs.sourceforge.net/viewvc/leaf/src/bering-uclibc/buildtool/ For starters, somebody who knows something about git (if that person was also a perl hacker, even better. But the code should be commented well enough that it should be possible to write the new code even without a great deal of perl knowledge). As far as I can see, in order for buildtool to work against a repository that's not cvs based, we need the corresponding implementation of CvsExt.pm, CvsPserver.pm, ViewCVS.pm in http://leaf.cvs.sourceforge.net/viewvc/leaf/src/bering-uclibc/buildtool/buildtool/DownloadTypes/ (most likely one implementation would be sufficient, since they all seem to be variations of the same thing) Once that's in place, the cvs-sourceforge server definition in http://leaf.cvs.sourceforge.net/viewvc/leaf/src/bering-uclibc/buildtool/conf/sources.cfg?revision=HEAD needs to be updated accordingly. If we still want the packages to be stored in the SCM system, and we still want the packages page and changelog to be be (semi-)automatically generated, the script http://leaf.cvs.sourceforge.net/viewvc/leaf/src/bering-uclibc/buildtool/tools/genpage.pl needs to be ported to work with the new SCM as well Just in case it's not obvious - I'm not volunteering for that job. To me, moving to a different SCM requires a lot of work, while not really solving a problem the project faces (IMHO) - unless I'm missing something, if all goes well and somebody spends the time on the migration and writing the new code for buildtool, we have pretty much the same we already have (the only difference would be the SCM being used). But of course, I'm not in a position to tell other people what they should or shouldn't do - I'm just trying to explain why I would have a hard time justifying spending my time on that (if I had that time at the moment). I may be able to help out with specific questions here and there, but at the moment, I don't have an awful lot of spare time on my hands. This task is the main thing holding up a move to git. Just out of curiosity - what features of git make it the SCM of choice for leaf? Seriously, all I know about it is that it is used to store the sources of the linux kernel. Martin -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] Buildtool
On Tue, 2010-04-06 at 22:08 +0200, Martin Hejl wrote: -snip- This task is the main thing holding up a move to git. Just out of curiosity - what features of git make it the SCM of choice for leaf? Seriously, all I know about it is that it is used to store the sources of the linux kernel. Martin, Git is very good at branch and merge operations. It's not the only scm SF is making available. Multiple repositories are available for most of the new offerings. This will allow us to have separate repositories for documentation and each leaf branch. https://sourceforge.net/apps/trac/sourceforge/wiki/What%20is%20Source%20Code%20Management? -- Mike Noyes mhnoyes at users.sourceforge.net http://sourceforge.net/users/mhnoyes/ SF.net Projects: leaf, sourceforge/sitedocs -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] Buildtool
On Tue, 2010-04-06 at 22:08 +0200, Martin Hejl wrote: Hi Mike, What assistance will help with 'buildtool' conversion from cvs to git? http://leaf.cvs.sourceforge.net/viewvc/leaf/src/bering-uclibc/buildtool/ -snip- If we still want the packages to be stored in the SCM system, Martin, I don't believe this is necessary any longer. SF now supports subdirectories in the FRS, making our previous pseudo-directory structure obsolete. I'll work on this tomorrow. https://sourceforge.net/apps/trac/sourceforge/wiki/Release%20files%20for%20download#Folders https://sourceforge.net/apps/trac/sourceforge/wiki/Release%20files%20for%20download#AccessingReleasesviaShell http://leaf.cvs.sourceforge.net/viewvc/*checkout*/leaf/sourceforge/docmanager/docid_1464.html?revision=1.3 and we still want the packages page and changelog to be be (semi-)automatically generated, the script http://leaf.cvs.sourceforge.net/viewvc/leaf/src/bering-uclibc/buildtool/tools/genpage.pl needs to be ported to work with the new SCM as well Port to trac wiki syntax. -- Mike Noyes mhnoyes at users.sourceforge.net http://sourceforge.net/users/mhnoyes/ SF.net Projects: leaf, sourceforge/sitedocs -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
