gnash-commit
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnash-commit] [SCM] Gnash branch, master, updated. release_0_8_9_fi


From: Sandro Santilli
Subject: Re: [Gnash-commit] [SCM] Gnash branch, master, updated. release_0_8_9_final-2127-g2e5e573
Date: Tue, 10 Jun 2014 12:46:46 +0200
User-agent: Mutt/1.5.21 (2010-09-15)

On Tue, Jun 10, 2014 at 09:50:48AM +0000, Bastiaan Jacques wrote:
> This is an automated email from the git hooks/post-receive script. It was
> generated because a ref change was pushed to the repository containing
> the project "Gnash".
> 
> The branch, master has been updated
>        via  2e5e5737faca9936e6a8645e69b380dddc52bf61 (commit)
>       from  9323a5502dad11f4c17ab3aa91fc2b0ea35b68c3 (commit)
> 
> Those revisions listed above that are new to this repository have
> not appeared on any other notification email; so we list those
> revisions in full, below.
> 
> - Log -----------------------------------------------------------------
> http://git.savannah.gnu.org/cgit//commit/?id=2e5e5737faca9936e6a8645e69b380dddc52bf61
> 
> 
> commit 2e5e5737faca9936e6a8645e69b380dddc52bf61
> Author: Bastiaan Jacques <address@hidden>
> Date:   Tue Jun 10 11:45:28 2014 +0200
> 
>     Switch the GcResource container type to forward_list.
>     
>     We don't make use of bidirectional access, so a singly linked list
>     is adequate. The order of elements seems to be irrelevant, so
>     it doesn't matter that we now push elements at the front rather
>     than the back.

I think the reason to push at the front and pop from the back was
the possible concurrent access to that list by different threads.

--strk;



reply via email to

[Prev in Thread] Current Thread [Next in Thread]