search for: feature_output_r

Displaying 7 results from an estimated 7 matches for "feature_output_r".

Did you mean: feature_output_re
2018 Jun 12
2
[PATCH] p2v: Allow virt-v2v input and output drivers containing '-' (RHBZ#1590220).
...ssh.c +++ b/p2v/ssh.c @@ -181,8 +181,8 @@ compile_regexps (void) 0); COMPILE (feature_libguestfs_rewrite_re, "libguestfs-rewrite", 0); COMPILE (feature_colours_option_re, "colours-option", 0); - COMPILE (feature_input_re, "input:((?:\\w)*)", 0); - COMPILE (feature_output_re, "output:((?:\\w)*)", 0); + COMPILE (feature_input_re, "input:((?:[-\\w])*)", 0); + COMPILE (feature_output_re, "output:((?:[-\\w])*)", 0); COMPILE (portfwd_re, "Allocated port ((?:\\d)+) for remote forward", 0); } -- 2.16.2
2018 Jun 12
1
Re: [PATCH] p2v: Allow virt-v2v input and output drivers containing '-' (RHBZ#1590220).
...regexps (void) > > 0); > > COMPILE (feature_libguestfs_rewrite_re, "libguestfs-rewrite", 0); > > COMPILE (feature_colours_option_re, "colours-option", 0); > > - COMPILE (feature_input_re, "input:((?:\\w)*)", 0); > > - COMPILE (feature_output_re, "output:((?:\\w)*)", 0); > > + COMPILE (feature_input_re, "input:((?:[-\\w])*)", 0); > > + COMPILE (feature_output_re, "output:((?:[-\\w])*)", 0); > > What about making them a bit more loose, e.g.: > > input:((?:[^\\n])+) > > so t...
2018 Jun 12
0
Re: [PATCH] p2v: Allow virt-v2v input and output drivers containing '-' (RHBZ#1590220).
...-181,8 +181,8 @@ compile_regexps (void) > 0); > COMPILE (feature_libguestfs_rewrite_re, "libguestfs-rewrite", 0); > COMPILE (feature_colours_option_re, "colours-option", 0); > - COMPILE (feature_input_re, "input:((?:\\w)*)", 0); > - COMPILE (feature_output_re, "output:((?:\\w)*)", 0); > + COMPILE (feature_input_re, "input:((?:[-\\w])*)", 0); > + COMPILE (feature_output_re, "output:((?:[-\\w])*)", 0); What about making them a bit more loose, e.g.: input:((?:[^\\n])+) so there are no further changes to do, in ca...
2018 Jun 21
0
[PATCH v2] p2v: Allow virt-v2v input and output drivers containing '-' (RHBZ#1590220).
...sh.c +++ b/p2v/ssh.c @@ -181,8 +181,11 @@ compile_regexps (void) 0); COMPILE (feature_libguestfs_rewrite_re, "libguestfs-rewrite", 0); COMPILE (feature_colours_option_re, "colours-option", 0); - COMPILE (feature_input_re, "input:((?:\\w)*)", 0); - COMPILE (feature_output_re, "output:((?:\\w)*)", 0); + /* The input and output regexps must match the same pattern in + * v2v/modules_list.ml. + */ + COMPILE (feature_input_re, "input:((?:[-\\w])+)", 0); + COMPILE (feature_output_re, "output:((?:[-\\w])+)", 0); COMPILE (portfwd_re, &q...
2018 Jun 21
2
p2v: Allow virt-v2v input and output drivers containing '-' (RHBZ#1590220).
v1 was here: https://www.redhat.com/archives/libguestfs/2018-June/msg00047.html v1 -> v2: - Add a regular expression in the virt-v2v modules code too. - - - I was planning a much more ambitious second version of this patch (half written too) which had: virt-v2v --describe-modules that listed a big chunk of XML which virt-p2v would parse. These would include the names of the
2016 Jun 18
8
[PATCH 0/7] p2v: Multiple improvements to the look of virt-p2v.
In the run dialog, I have implemented an ANSI colour escape sequence interpreter, so that colours displayed by the remote virt-v2v are now shown to the user. (https://bugzilla.redhat.com/show_bug.cgi?id=1314244) This requires virt-v2v to send colours. It wasn't doing that because the output was a pipe (as we capture the output into the log file). So I added a global --colours option to make
2019 Sep 10
3
[PATCH 0/2] Remove virt-p2v from libguestfs
Now that virt-p2v has its own repository [1] and releases [2], it is time to remove it from libguestfs. [1] https://github.com/libguestfs/virt-p2v [2] http://download.libguestfs.org/virt-p2v/ Pino Toscano (2): Remove virt-p2v Remove remaining virt-p2v bits .gitignore | 4 - Makefile.am | 7 +- bash/Makefile.am