[CRIU] c-lib: sending additional patches that rely on previous patches

[Radostin Stoyanov]

Hi Martin

On 17/01/2019 08:45, Martin Wuehrer wrote:
> Hy
> What is the current status of the c-lib patches, that were sent by me?
>
> - "[CRIU] [PATCH 1/2] c-lib: fixed memleaks, add criu_local_free_opts()
> " from Fri Dec 21 10:00:20 MSK 2018 
> - "[CRIU] [PATCH 2/2] c-lib: converted `char *`-args to `const char *`"
> from Fri Dec 21 10:00:21 MSK 2018
> - "[CRIU] [PATCH v2 1/2] c-lib: fixed memleaks, add
> criu_local_free_opts()" from Mon Jan 7 11:20:43 MSK 2019)?
>
> Because currently I have another patch that relies on them. 
>
> Should I wait until they are applied upstream (since they are planned
> to be merged soon) or should I send another patch mail, where I mention
> in the message that it relies on the previous patches.
>
> I am asking also because the automatic CI-checks would fail for the new
> patch since it relies on the previous patches that are currently not
> upstream.
Would it be possible to send/resend the patches you have in a new patch
series that could applied on the criu-dev branch?
This will make it easier to be reviewed.

Thanks,
Radostin