[cairo] API Shakeup: Eliminating cairo_copy

[Banlu Kemiyatorn]

On Wed, 23 Feb 2005 09:33:49 -0500, Carl Worth <cworth at cworth.org> wrote:

> This second point should be well addressed by the thread:
> 
>         API Shakeup: cairo_create and eliminating cairo_set_target_surface
> 
> The original confusion regarding the behavior of cairo_copy still
> remains.
> 
> We discussed this and decided to simply eliminate the cairo_copy call.
> 
> Then, if a use case arises where some additional functions are needed,
> (such as cairo_get/set_graphics_state), we can easily add them in the
> future. But we don't know any compelling reason to do so now.

Hi, I can't find the previous thread and this confused me.
How do I store the current graphic state without copy or set/get?
Or do I need to construct a state manually?