Re: [leaf-devel] next steps

2011-02-12 Thread Andrew
12.02.2011 12:39, davidMbrooke пишет: > On Wed, 2011-02-09 at 23:50 +0200, Andrew wrote: >> 09.02.2011 00:05, KP Kirchdoerfer пишет: >>> Am Sonntag, 6. Februar 2011, um 12:14:16 schrieb ads...@genis-x.com: Is anyone able to push all the contrib packages into git? >>> All package sources has be

Re: [leaf-devel] next steps

2011-02-12 Thread davidMbrooke
On Wed, 2011-02-09 at 23:50 +0200, Andrew wrote: > 09.02.2011 00:05, KP Kirchdoerfer пишет: > > Am Sonntag, 6. Februar 2011, um 12:14:16 schrieb ads...@genis-x.com: > >> Is anyone able to push all the contrib packages into git? > > All package sources has been moved into git. > > kp: Thank you. I

Re: [leaf-devel] next steps

2011-02-09 Thread Andrew
09.02.2011 00:05, KP Kirchdoerfer пишет: > Am Sonntag, 6. Februar 2011, um 12:14:16 schrieb ads...@genis-x.com: >> Is anyone able to push all the contrib packages into git? > All package sources has been moved into git. > > Pls test and give feedback if it works - or report back errors you detect

Re: [leaf-devel] next steps

2011-02-08 Thread KP Kirchdoerfer
Am Sonntag, 6. Februar 2011, um 12:14:16 schrieb ads...@genis-x.com: > Is anyone able to push all the contrib packages into git? All package sources has been moved into git. Pls test and give feedback if it works - or report back errors you detect while building the packages. thx kp -

Re: [leaf-devel] next steps

2011-02-06 Thread davidMbrooke
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

Re: [leaf-devel] next steps

2011-02-06 Thread davidMbrooke
- 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

Re: [leaf-devel] next steps

2011-02-06 Thread davidMbrooke
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/

Re: [leaf-devel] next steps

2011-02-06 Thread adstar
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

Re: [leaf-devel] next steps

2011-02-05 Thread davidMbrooke
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

Re: [leaf-devel] next steps

2011-02-03 Thread Andrew
03.02.2011 17:07, Mike Noyes пишет: > 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

Re: [leaf-devel] next steps

2011-02-03 Thread Mike Noyes
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 commi

Re: [leaf-devel] next steps

2011-02-01 Thread Andrew
01.02.2011 22:42, Mike Noyes пишет: > On Tue, 2011-02-01 at 22:27 +0200, Andrew wrote: >> 01.02.2011 17:37, Mike Noyes пишет: >>> On Tue, 2011-02-01 at 14:15 +0200, Andrew wrote: 01.02.2011 14:02, KP Kirchdoerfer пишет: > Am Dienstag, 1. Februar 2011, um 12:45:00 schrieb Andrew: >> 31.

Re: [leaf-devel] next steps

2011-02-01 Thread Charles Steinkuehler
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2/1/2011 2:42 PM, Mike Noyes wrote: > On Tue, 2011-02-01 at 22:27 +0200, Andrew wrote: >> For completion I need that somebody push latest available snapshot into >> git with modified server names into packages (cvs-sourceforge is >> replaced by le

Re: [leaf-devel] next steps

2011-02-01 Thread Mike Noyes
On Tue, 2011-02-01 at 22:27 +0200, Andrew wrote: > 01.02.2011 17:37, Mike Noyes пишет: > > On Tue, 2011-02-01 at 14:15 +0200, Andrew wrote: > >> 01.02.2011 14:02, KP Kirchdoerfer пишет: > >>> Am Dienstag, 1. Februar 2011, um 12:45:00 schrieb Andrew: > 31.01.2011 23:06, Mike Noyes пишет: >

Re: [leaf-devel] next steps

2011-02-01 Thread Andrew
01.02.2011 17:37, Mike Noyes пишет: > On Tue, 2011-02-01 at 14:15 +0200, Andrew wrote: >> 01.02.2011 14:02, KP Kirchdoerfer пишет: >>> Am Dienstag, 1. Februar 2011, um 12:45:00 schrieb Andrew: 31.01.2011 23:06, Mike Noyes пишет: > Charles, > I just enabled svn for our project again. Gi

Re: [leaf-devel] next steps

2011-02-01 Thread Mike Noyes
On Tue, 2011-02-01 at 14:15 +0200, Andrew wrote: > 01.02.2011 14:02, KP Kirchdoerfer пишет: > > Am Dienstag, 1. Februar 2011, um 12:45:00 schrieb Andrew: > >> 31.01.2011 23:06, Mike Noyes пишет: > >>> Charles, > >>> I just enabled svn for our project again. Git is enabled also, but I > >>> suspect

Re: [leaf-devel] next steps

2011-02-01 Thread Andrew
01.02.2011 14:02, KP Kirchdoerfer пишет: > Am Dienstag, 1. Februar 2011, um 12:45:00 schrieb Andrew: >> 31.01.2011 23:06, Mike Noyes пишет: >>> Charles, >>> I just enabled svn for our project again. Git is enabled also, but I >>> suspect migration to git is more complex. >> I think that migration t

Re: [leaf-devel] next steps

2011-02-01 Thread KP Kirchdoerfer
Am Dienstag, 1. Februar 2011, um 12:45:00 schrieb Andrew: > 31.01.2011 23:06, Mike Noyes пишет: > > Charles, > > I just enabled svn for our project again. Git is enabled also, but I > > suspect migration to git is more complex. > > I think that migration to any SCM is trivial till it's possible to

Re: [leaf-devel] next steps

2011-02-01 Thread Andrew
31.01.2011 23:06, Mike Noyes пишет: > Charles, > I just enabled svn for our project again. Git is enabled also, but I > suspect migration to git is more complex. I think that migration to any SCM is trivial till it's possible to get access to source tree (latest version of files) via HTTP. And git

Re: [leaf-devel] next steps

2011-01-31 Thread Mike Noyes
On Mon, 2011-01-31 at 15:18 -0600, Charles Steinkuehler wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 1/31/2011 3:06 PM, Mike Noyes wrote: > > SVN Admin > > https://sourceforge.net/project/admin/svn.php?group_id=13751 > > > > KP, Martin, Andrew, and the rest of the Bering team c

Re: [leaf-devel] next steps

2011-01-31 Thread Charles Steinkuehler
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 1/31/2011 3:06 PM, Mike Noyes wrote: > SVN Admin > https://sourceforge.net/project/admin/svn.php?group_id=13751 > > KP, Martin, Andrew, and the rest of the Bering team can provide you with > migration issues. Thanks! What's the current status of

Re: [leaf-devel] next steps

2011-01-31 Thread Mike Noyes
On Mon, 2011-01-31 at 13:58 -0600, Charles Steinkuehler wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 1/31/2011 12:54 PM, Mike Noyes wrote: > > On Mon, 2011-01-31 at 17:37 +0100, KP Kirchdoerfer wrote: > > -snip- > >> And it might be a good base, to make a step back and rework ou

Re: [leaf-devel] next steps

2011-01-31 Thread Charles Steinkuehler
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 1/31/2011 12:54 PM, Mike Noyes wrote: > On Mon, 2011-01-31 at 17:37 +0100, KP Kirchdoerfer wrote: > -snip- >> And it might be a good base, to make a step back and rework our >> infrastructure. This could be work on buildenv to support more platform

Re: [leaf-devel] next steps

2011-01-31 Thread Mike Noyes
On Mon, 2011-01-31 at 17:37 +0100, KP Kirchdoerfer wrote: -snip- > And it might be a good base, to make a step back and rework our > infrastructure. This could be work on buildenv to support more platforms, or > more possibly, we may be forced to move away from cvs I don't like to > make, or