Re: [Gnash-dev] Re: Burning 100% CPU time: MediaParser/FLVParser never pauses

2010-08-13 Thread strk
On Thu, Aug 12, 2010 at 09:46:07PM -0600, Rob Savoye wrote: On 08/12/10 07:47, strk wrote: I'm working on a patch for testing if you don't beat me to it. The patch would also make waitIfNeeded() I just merged your patch into the git master branch (and not the release branch), but next

Re: [Gnash-dev] Re: Burning 100% CPU time: MediaParser/FLVParser never pauses

2010-08-13 Thread Andrea Palmatè
Il giorno 13/ago/2010, alle ore 05.46, Rob Savoye ha scritto: I'm considering turning off bzr access this weekend unless anyone complains. We can use git-bzr-ng to import any bzr branches into git so they don't get lost. Importing from bzr works, but is slow as usual... what about

Re: [Gnash-dev] BSD testing

2010-08-13 Thread strk
On Thu, Aug 12, 2010 at 09:55:25PM -0600, Rob Savoye wrote: If any BSD users out there can test the release branch, I'd appreciate it. I'll get around to it next week now that the release branch is mostly stabilized, but I'd need to upgrade my builds slaves to the most recent versions, which

Re: [Gnash-dev] Re: Burning 100% CPU time: MediaParser/FLVParser never pauses

2010-08-13 Thread strk
On Fri, Aug 13, 2010 at 11:03:19AM +0200, strk wrote: On Thu, Aug 12, 2010 at 09:46:07PM -0600, Rob Savoye wrote: On 08/12/10 07:47, strk wrote: I'm working on a patch for testing if you don't beat me to it. The patch would also make waitIfNeeded() I just merged your patch into

Re: [Gnash-dev] Re: Burning 100% CPU time: MediaParser/FLVParser never pauses

2010-08-13 Thread Rob Savoye
On 08/13/10 03:35, Andrea Palmatè wrote: what about passwords? will be the same? Nothing seems to have changed for me password wise with git. - rob - ___ Gnash-dev mailing list Gnash-dev@gnu.org

Re: [Gnash-dev] Re: Burning 100% CPU time: MediaParser/FLVParser never pauses

2010-08-13 Thread Rob Savoye
On 08/13/10 04:54, strk wrote: Should we put the waitIfNeeded change in branch too ? I think it'd be nice for the coming release to be easier on CPU (if that patch is tested enough to be safe) The is tested enough being the key point. We should do some more testing now that this is in

Re: [Gnash-dev] BSD testing

2010-08-13 Thread Robinson Tryon
On Fri, Aug 13, 2010 at 6:50 AM, strk s...@keybit.net wrote: At least with git version 1.6.0.2 I belive the branch command should also specify which remote branch to track, or will be a private branch with that name, so I had to do this: $ git clone git://git.sv.gnu.org/gnash.git $ git

Re: [Gnash-dev] BSD testing

2010-08-13 Thread Rob Savoye
On 08/13/10 04:50, strk wrote: On Thu, Aug 12, 2010 at 09:55:25PM -0600, Rob Savoye wrote: At least with git version 1.6.0.2 I belive the branch command should also specify which remote branch to track, or will be a private branch with that name, so I had to do this: $ git clone

Re: [Gnash-dev] BSD testing

2010-08-13 Thread strk
On Fri, Aug 13, 2010 at 08:40:44AM -0600, Rob Savoye wrote: And I think this helps merging: (still learning git) [branch release_0_8_8] remote = origin merge = refs/heads/release_0_8_8 I belive the above lines are what you get by adding the second argument to checkout or branch