Displaying 5 results from an estimated 5 matches for "tar_get_readi".
Did you mean:
tar_get_ready
2020 Jul 06
2
Re: [PATCH nbdkit 2/2] tar: Rewrite the tar plugin (again), this time in C.
On 6/28/20 8:02 AM, Richard W.M. Jones wrote:
> ---
> plugins/tar/{tar.pl => nbdkit-tar-plugin.pod} | 145 ++-------
> configure.ac | 2 -
> plugins/tar/Makefile.am | 41 +--
> tests/Makefile.am | 14 +-
> plugins/tar/tar.c | 286 ++++++++++++++++++
>
2020 Jun 28
5
[PATCH nbdkit 0/2] tar: Rewrite the tar plugin (again), this time in C.
For context see these threads:
https://lists.gnu.org/archive/html/qemu-discuss/2020-06/threads.html#00053
https://lists.gnu.org/archive/html/qemu-block/2020-06/threads.html#01496
Rich.
2020 Jun 28
2
Re: [PATCH nbdkit 2/2] tar: Rewrite the tar plugin (again), this time in C.
On Sun, Jun 28, 2020 at 4:03 PM Richard W.M. Jones <rjones@redhat.com> wrote:
...
> +
> +static int
> +tar_get_ready (void)
> +{
> + FILE *fp;
> + CLEANUP_FREE char *cmd = NULL;
> + size_t len = 0;
> + bool scanned_ok;
> + char s[256];
> +
> + /* Construct the tar command to examine the tar file. */
> + fp = open_memstream (&cmd, &len);
>
2020 Jul 06
0
Re: [PATCH nbdkit 2/2] tar: Rewrite the tar plugin (again), this time in C.
On Mon, Jul 06, 2020 at 01:58:35PM -0500, Eric Blake wrote:
> so if we like the idea, we'd have to allow the user to specify
> mutually-exclusive config parameters: either file= to something
> within the file, or exportname=on to allow the client to choose,
> where we then validate that exactly one of those two options is
> configured.
Right, I think that would be the way to do
2020 Jun 28
0
[PATCH nbdkit 2/2] tar: Rewrite the tar plugin (again), this time in C.
---
plugins/tar/{tar.pl => nbdkit-tar-plugin.pod} | 145 ++-------
configure.ac | 2 -
plugins/tar/Makefile.am | 41 +--
tests/Makefile.am | 14 +-
plugins/tar/tar.c | 286 ++++++++++++++++++
tests/test-dump-plugin.sh | 2 +-
tests/test-help-plugin.sh