Diff comments:
> diff --git a/doc/topics/config.rst b/doc/topics/config.rst
> index ff766c7..9e3eab5 100644
> --- a/doc/topics/config.rst
> +++ b/doc/topics/config.rst
> @@ -363,6 +363,17 @@ If this key is set to the string 'disabled' then curtin
> will not
> unmount the target filesystem when install is complete. This
> skips unmounting in all cases of install success or failure.
>
> +**export_resume_data**: *<path to where to export the data needed to resume>*
OK, I understand better what's going on.
I do think I would like to relax things a bit and make it so that only one
resume_data directive is needed. This means the first invocation should be
comfortable with the non-existance of the resume data, maybe a quick log
statement like "resume data not found, creating" could cover that.
On the subject of the log files, I think we should unify then for easier
reading by Administrators. This suggests that curtin should be able to append
to an existing log file, perhaps by default or a command line option to enable
that behavior would be OK.
> +
> +When specified, curtin will export in the file specified the data required to
> +resume the installation and run further stages.
> +
> +**import_resume_data**: *<path from where to import the data needed to
> resume>*
> +
> +When specified, curtin will consider that the installation has already been
> +initiated and will load the data from the file specified. The target
> directory
> +will not be expected to be empty.
> +
> **Example**::
>
> install:
--
https://code.launchpad.net/~ogayot/curtin/+git/curtin/+merge/427671
Your team curtin developers is subscribed to branch curtin:master.
--
Mailing list: https://launchpad.net/~curtin-dev
Post to : curtin-dev@lists.launchpad.net
Unsubscribe : https://launchpad.net/~curtin-dev
More help : https://help.launchpad.net/ListHelp
