search for: cd49063

...$h->node_name ($a) cmp $h->node_name ($b) } @children; - reg_export_node ($h, $_, $fh, @_) foreach @children; + reg_export_node ($h, $_, $fh, $depth + 1, @_) foreach @children; } # Escape " and \ when printing keys. diff --git a/regedit/hivexregedit b/regedit/hivexregedit index cd49063..737450d 100755 --- a/regedit/hivexregedit +++ b/regedit/hivexregedit @@ -259,6 +259,20 @@ Use heuristics to tolerate certain levels of corruption within hives. This is unsafe but may allow to export/merge valid keys/values in an othewise corrupted hive. +=cut + +my $max_depth; + +=item B<--...

Put the "=back" to close the list only after the last element. --- regedit/hivexregedit | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/regedit/hivexregedit b/regedit/hivexregedit index 02c382b..cd49063 100755 --- a/regedit/hivexregedit +++ b/regedit/hivexregedit @@ -248,8 +248,6 @@ You should only use this option for quick hacking and debugging of the hive contents, and I<never> use it if the output is going to be passed into another program or stored in another hive. -=back - =cut...

This new option allows you to only export what you care about from a registry hive by specifying a max recursion depth. Michael Meyer (1): hivexregedit: add --max-depth option for exports perl/lib/Win/Hivex/Regedit.pm | 14 ++++++++++++-- regedit/hivexregedit | 18 +++++++++++++++++- 2 files changed, 29 insertions(+), 3 deletions(-) -- 2.14.3 (Apple Git-98)