We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
If one has following structure producing /foo object
/foo
$ tree . └── foo └── main.fmf
adding another fmf file makes the original node stop being leaf and thus disapearing from the fmf tree
$ tree . └── foo ├── bar.fmf └── main.fmf $ fmf ls /foo/bar
Proposal to add marker similar to /: inherit:false which would keep the /foo being an object, thus for the above tree we will have:
/: inherit:false
$ fmf ls /foo /foo/bar
Name of the marker subject to discussion: how about retain-name?
retain-name
Related tmt issue: tmt/issues/1795
The text was updated successfully, but these errors were encountered:
Another name proposal: is-leaf
is-leaf
Sorry, something went wrong.
Add directive is-leaf to force selecting node
e7d1464
Expected usage with virtual tests while keeping the parent test as well Fix: #221
make-leaf
543e52a
Successfully merging a pull request may close this issue.
If one has following structure producing
/foo
objectadding another fmf file makes the original node stop being leaf and thus disapearing from the fmf tree
Proposal to add marker similar to
/: inherit:false
which would keep the/foo
being an object, thus for the above tree we will have:Name of the marker subject to discussion: how about
retain-name
?Related tmt issue: tmt/issues/1795
The text was updated successfully, but these errors were encountered: