Re: [leaf-devel] next steps
On Sat, 2011-02-05 at 12:32 +, davidMbrooke wrote: > On Thu, 2011-02-03 at 07:07 -0800, Mike Noyes wrote: > > On Tue, 2011-02-01 at 23:08 +0200, Andrew wrote: > > > This is quite easy: do git clone and set personal data (name/email); > > > copy bering-uclibc/apps and bering-uclibc/contrib into git dir; modify > > > config files (replace server names) into sources' buildenv.conf; do git > > > add * and then do git commit and git push. > > > After short look in leaf-commits mailing list, in current git snapshot > > > only last busybox commit (update to 1.18.2) is missed. > > > > Andrew, > > Is git functional for continued development, or are further actions > > necessary? > > > > Everyone, > > Here are a few links to help everyone get up to speed on git: > > > > http://sourceforge.net/apps/trac/sourceforge/wiki/Git > > http://www.kernel.org/pub/software/scm/git/docs/gittutorial.html > > http://git-scm.com/documentation > > > > GitWeb > > http://leaf.git.sourceforge.net/ > > Thanks Mike. I have created a new wiki page for hints and tips on using > Git for LEAF as Appendix 2 in the Developer Guide, direct link is: > http://sourceforge.net/apps/mediawiki/leaf/index.php?title=Bering-uClibc_4.x_-_Developer_Guide_-_Hints_and_Tips_for_using_Git_SCM > > Personally I am new to Git and I plan to spend several hours > investigating it over the weekend. I have already spotted some things > that I think could be improved (see the Discussion page on the wiki) so > I suggest the main developers review the status in a couple of days. > I have no doubt that Git is the right new SCM tool for LEAF but it has > some different concepts from CVS and we may need to refine our approach. > > dMb Personally I am now through the pain barrier with Git, so I'm happy to use it in preference to CVS from now on. In fact, I'm *almost* at the point where I prefer it to CVS, though I keep typing "cvs add" by mistake... :-) Are we all agreed on that - do we now use Git even when (if?) CVS comes back on line? I believe the -beta2 busybox update is still missing in the Git snapshot, and as per other mails on this list there are still many packages to migrate from the pre-4.x CVS branch. dMb -- The modern datacenter depends on network connectivity to access resources and provide services. The best practices for maximizing a physical server's connectivity to a physical network are well understood - see how these rules translate into the virtual world? http://p.sf.net/sfu/oracle-sfdevnlfb ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] next steps
On Sun, 2011-02-06 at 12:17 +, davidMbrooke wrote: > On Sun, 2011-02-06 at 22:14 +1100, ads...@genis-x.com wrote: > > Is anyone able to push all the contrib packages into git? > > Hi Ad, > > Your messages aren't showing up in leaf-devel for some reason, even > though you seem to specify the right address in the "Cc:" field. > > There are people with the capability to push to git, but maybe they > don't have the time or the motivation right now :-) > > I see that kp has made a start (haserl and pwcrypt). > > Do you have a definitive list of what is missing? I can do a few > Packages but I don't have time to do 20. I am still learning Git (and > writing the Wiki page as I go) which slows things down. > > I suspect that Git is also wide open for write access right now, so > others could help with this job if we can co-ordinate the team. > > dMb I have added a few of the missing source Packages: - keyboard - hdparm (which was WAY out of date so I upgraded to the latest) - this also fixes the failure on hdsupp - upnpbridge - pcre (also old so I upgraded) - this also fixes the failure on kismet Plenty more to fix though! dMb > > -Original Message- > > From: davidMbrooke [mailto:dmb.leaf-de...@ntlworld.com] > > Sent: Saturday, 5 February 2011 11:32 PM > > To: leaf-devel > > Subject: Re: [leaf-devel] next steps > > > > On Thu, 2011-02-03 at 07:07 -0800, Mike Noyes wrote: > > > On Tue, 2011-02-01 at 23:08 +0200, Andrew wrote: > > > > This is quite easy: do git clone and set personal data (name/email); > > > > copy bering-uclibc/apps and bering-uclibc/contrib into git dir; > > > > modify config files (replace server names) into sources' > > > > buildenv.conf; do git add * and then do git commit and git push. > > > > After short look in leaf-commits mailing list, in current git > > > > snapshot only last busybox commit (update to 1.18.2) is missed. > > > > > > Andrew, > > > Is git functional for continued development, or are further actions > > > necessary? > > > > > > Everyone, > > > Here are a few links to help everyone get up to speed on git: > > > > > > http://sourceforge.net/apps/trac/sourceforge/wiki/Git > > > http://www.kernel.org/pub/software/scm/git/docs/gittutorial.html > > > http://git-scm.com/documentation > > > > > > GitWeb > > > http://leaf.git.sourceforge.net/ > > > > Thanks Mike. I have created a new wiki page for hints and tips on using Git > > for LEAF as Appendix 2 in the Developer Guide, direct link is: > > http://sourceforge.net/apps/mediawiki/leaf/index.php?title=Bering-uClibc_4.x > > _-_Developer_Guide_-_Hints_and_Tips_for_using_Git_SCM > > > > Personally I am new to Git and I plan to spend several hours investigating > > it over the weekend. I have already spotted some things that I think could > > be improved (see the Discussion page on the wiki) so I suggest the main > > developers review the status in a couple of days. > > I have no doubt that Git is the right new SCM tool for LEAF but it has some > > different concepts from CVS and we may need to refine our approach. > > > > dMb -- The modern datacenter depends on network connectivity to access resources and provide services. The best practices for maximizing a physical server's connectivity to a physical network are well understood - see how these rules translate into the virtual world? http://p.sf.net/sfu/oracle-sfdevnlfb ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] Future "Milestones" for Trac
On Sun, 2011-02-06 at 16:28 +0100, KP Kirchdoerfer wrote: > Am Sonntag, 6. Februar 2011, um 15:34:18 schrieb davidMbrooke: > > Hi kp, > > > > Please would you add some future "Milestones" to Trac. > > There are changes / enhancements I would like to flag up for 4.1 and > > right now we have nothing beyond 4.0.1. > > > > Maybe add 4.1 and 4.2 ? > > > > Thanks, > > > > dMb > > done > > kp Thanks very much. Now "Active Tickets by Milestone" is in a more sensible order, at least for my personal view of priorities. dMb -- The modern datacenter depends on network connectivity to access resources and provide services. The best practices for maximizing a physical server's connectivity to a physical network are well understood - see how these rules translate into the virtual world? http://p.sf.net/sfu/oracle-sfdevnlfb ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] Future "Milestones" for Trac
Am Sonntag, 6. Februar 2011, um 15:34:18 schrieb davidMbrooke: > Hi kp, > > Please would you add some future "Milestones" to Trac. > There are changes / enhancements I would like to flag up for 4.1 and > right now we have nothing beyond 4.0.1. > > Maybe add 4.1 and 4.2 ? > > Thanks, > > dMb done kp -- The modern datacenter depends on network connectivity to access resources and provide services. The best practices for maximizing a physical server's connectivity to a physical network are well understood - see how these rules translate into the virtual world? http://p.sf.net/sfu/oracle-sfdevnlfb ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
[leaf-devel] Future "Milestones" for Trac
Hi kp, Please would you add some future "Milestones" to Trac. There are changes / enhancements I would like to flag up for 4.1 and right now we have nothing beyond 4.0.1. Maybe add 4.1 and 4.2 ? Thanks, dMb -- The modern datacenter depends on network connectivity to access resources and provide services. The best practices for maximizing a physical server's connectivity to a physical network are well understood - see how these rules translate into the virtual world? http://p.sf.net/sfu/oracle-sfdevnlfb ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] next steps
On Sun, 2011-02-06 at 22:14 +1100, ads...@genis-x.com wrote: > Is anyone able to push all the contrib packages into git? Hi Ad, Your messages aren't showing up in leaf-devel for some reason, even though you seem to specify the right address in the "Cc:" field. There are people with the capability to push to git, but maybe they don't have the time or the motivation right now :-) I see that kp has made a start (haserl and pwcrypt). Do you have a definitive list of what is missing? I can do a few Packages but I don't have time to do 20. I am still learning Git (and writing the Wiki page as I go) which slows things down. I suspect that Git is also wide open for write access right now, so others could help with this job if we can co-ordinate the team. dMb > -Original Message- > From: davidMbrooke [mailto:dmb.leaf-de...@ntlworld.com] > Sent: Saturday, 5 February 2011 11:32 PM > To: leaf-devel > Subject: Re: [leaf-devel] next steps > > On Thu, 2011-02-03 at 07:07 -0800, Mike Noyes wrote: > > On Tue, 2011-02-01 at 23:08 +0200, Andrew wrote: > > > This is quite easy: do git clone and set personal data (name/email); > > > copy bering-uclibc/apps and bering-uclibc/contrib into git dir; > > > modify config files (replace server names) into sources' > > > buildenv.conf; do git add * and then do git commit and git push. > > > After short look in leaf-commits mailing list, in current git > > > snapshot only last busybox commit (update to 1.18.2) is missed. > > > > Andrew, > > Is git functional for continued development, or are further actions > > necessary? > > > > Everyone, > > Here are a few links to help everyone get up to speed on git: > > > > http://sourceforge.net/apps/trac/sourceforge/wiki/Git > > http://www.kernel.org/pub/software/scm/git/docs/gittutorial.html > > http://git-scm.com/documentation > > > > GitWeb > > http://leaf.git.sourceforge.net/ > > Thanks Mike. I have created a new wiki page for hints and tips on using Git > for LEAF as Appendix 2 in the Developer Guide, direct link is: > http://sourceforge.net/apps/mediawiki/leaf/index.php?title=Bering-uClibc_4.x > _-_Developer_Guide_-_Hints_and_Tips_for_using_Git_SCM > > Personally I am new to Git and I plan to spend several hours investigating > it over the weekend. I have already spotted some things that I think could > be improved (see the Discussion page on the wiki) so I suggest the main > developers review the status in a couple of days. > I have no doubt that Git is the right new SCM tool for LEAF but it has some > different concepts from CVS and we may need to refine our approach. > > dMb -- The modern datacenter depends on network connectivity to access resources and provide services. The best practices for maximizing a physical server's connectivity to a physical network are well understood - see how these rules translate into the virtual world? http://p.sf.net/sfu/oracle-sfdevnlfb ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] LEAF Website Error from "Packages 4.x" page
On Sun, 2011-02-06 at 07:16 +0100, KP Kirchdoerfer wrote: > Am Samstag, 5. Februar 2011, um 20:36:43 schrieb davidMbrooke: > > Hi kp, > > > > I notice that the Bering-uClibc "Packages 4.x" page is giving an error. > > > > Error is: XML Parsing Error: not well-formed > > Location: > > http://leaf.sourceforge.net/bering-uclibc/index.php?module=pagemaster&PAGE_ > > user_op=view_page&PAGE_id=13&MMN_position=33:33 Line Number 784, Column > > 54:Homepage: > href="https://fedorahosted.org/elfutils/">https://fedorahosted.org/elfu > > tils/ -^ > > > > Are you able to fix? > > > > Thanks, > > > > dMb > > I think it's fixed for today; don't what it caused and can't test without cvs > access. > > kp Thanks. It is indeed fixed (for now). Hopefully CVS will be back soon. dMb -- The modern datacenter depends on network connectivity to access resources and provide services. The best practices for maximizing a physical server's connectivity to a physical network are well understood - see how these rules translate into the virtual world? http://p.sf.net/sfu/oracle-sfdevnlfb ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] next steps
Is anyone able to push all the contrib packages into git? -Original Message- From: davidMbrooke [mailto:dmb.leaf-de...@ntlworld.com] Sent: Saturday, 5 February 2011 11:32 PM To: leaf-devel Subject: Re: [leaf-devel] next steps On Thu, 2011-02-03 at 07:07 -0800, Mike Noyes wrote: > On Tue, 2011-02-01 at 23:08 +0200, Andrew wrote: > > This is quite easy: do git clone and set personal data (name/email); > > copy bering-uclibc/apps and bering-uclibc/contrib into git dir; > > modify config files (replace server names) into sources' > > buildenv.conf; do git add * and then do git commit and git push. > > After short look in leaf-commits mailing list, in current git > > snapshot only last busybox commit (update to 1.18.2) is missed. > > Andrew, > Is git functional for continued development, or are further actions > necessary? > > Everyone, > Here are a few links to help everyone get up to speed on git: > > http://sourceforge.net/apps/trac/sourceforge/wiki/Git > http://www.kernel.org/pub/software/scm/git/docs/gittutorial.html > http://git-scm.com/documentation > > GitWeb > http://leaf.git.sourceforge.net/ Thanks Mike. I have created a new wiki page for hints and tips on using Git for LEAF as Appendix 2 in the Developer Guide, direct link is: http://sourceforge.net/apps/mediawiki/leaf/index.php?title=Bering-uClibc_4.x _-_Developer_Guide_-_Hints_and_Tips_for_using_Git_SCM Personally I am new to Git and I plan to spend several hours investigating it over the weekend. I have already spotted some things that I think could be improved (see the Discussion page on the wiki) so I suggest the main developers review the status in a couple of days. I have no doubt that Git is the right new SCM tool for LEAF but it has some different concepts from CVS and we may need to refine our approach. dMb -- The modern datacenter depends on network connectivity to access resources and provide services. The best practices for maximizing a physical server's connectivity to a physical network are well understood - see how these rules translate into the virtual world? http://p.sf.net/sfu/oracle-sfdevnlfb ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel -- The modern datacenter depends on network connectivity to access resources and provide services. The best practices for maximizing a physical server's connectivity to a physical network are well understood - see how these rules translate into the virtual world? http://p.sf.net/sfu/oracle-sfdevnlfb ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
