Function svn_repos_get_fs_build_parser6 

pub unsafe extern "C" fn svn_repos_get_fs_build_parser6(
    parser: *mut *const svn_repos_parse_fns3_t,
    parse_baton: *mut *mut c_void,
    repos: *mut svn_repos_t,
    start_rev: svn_revnum_t,
    end_rev: svn_revnum_t,
    use_history: svn_boolean_t,
    validate_props: svn_boolean_t,
    uuid_action: svn_repos_load_uuid,
    parent_dir: *const c_char,
    use_pre_commit_hook: svn_boolean_t,
    use_post_commit_hook: svn_boolean_t,
    ignore_dates: svn_boolean_t,
    normalize_props: svn_boolean_t,
    notify_func: svn_repos_notify_func_t,
    notify_baton: *mut c_void,
    pool: *mut apr_pool_t,
) -> *mut svn_error_t

Set @a *parser and @a *parse_baton to a vtable parser which commits new revisions to the fs in @a repos. The constructed parser will treat UUID records in a manner consistent with @a uuid_action. Use @a pool to operate on the fs.

@a start_rev and @a end_rev act as filters, the lower and upper (inclusive) range values of revisions which will be loaded. Either both of these values are #SVN_INVALID_REVNUM (in which case no revision-based filtering occurs at all), or both are valid revisions (where @a start_rev is older than or equivalent to @a end_rev). They refer to dump stream revision numbers rather than committed revision numbers.

If @a use_history is true, then when the parser encounters a node that is added-with-history, it will require ‘copy-from’ history to exist in the repository at the relative (adjusted) copy-from revision and path. It will perform a copy from that source location, and will fail if no suitable source exists there. If @a use_history is false, then it will instead convert every copy to a plain add.

The ‘use_history=FALSE’ case is unused and untested in Subversion.

It seems to me it would not work with a deltas dumpfile (a driver
that calls the @c apply_textdelta method), as it would not have
access to the delta base text.

If @a use_pre_commit_hook is set, call the repository’s pre-commit hook before committing each loaded revision.

If @a use_post_commit_hook is set, call the repository’s post-commit hook after committing each loaded revision.

If @a validate_props is set, then validate Subversion revision and node properties (those in the svn: namespace) against established rules for those things.

If @a ignore_dates is set, ignore any revision datestamps found in @a dumpstream, allowing the revisions created by the load process to be stamped as if they were newly created via the normal commit process.

If @a normalize_props is set, attempt to normalize invalid Subversion revision and node properties (those in the svn: namespace) so that their values would follow the established rules for them. For example, for such properties, typically the value must be in UTF-8 with LF line endings.

@note The details or the performed normalizations are deliberately left unspecified and may change in the future.

If @a parent_dir is not NULL, then the parser will reparent all the loaded nodes, from root to @a parent_dir. The directory @a parent_dir must be an existing directory in the repository.

@since New in 1.10.