Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

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

Jump to bottom

Parent file reference traversal. #2061

Closed
MariasStory opened this issue Aug 1, 2018 · 2 comments
Closed

Parent file reference traversal. #2061

MariasStory opened this issue Aug 1, 2018 · 2 comments
Assignees
@Onager
Labels
duplicate Duplicate of another issue enhancement New or improved functionality

Comments

@MariasStory
Copy link

MariasStory commented Aug 1, 2018 •
edited
Loading

The "Parent file reference:" entries are confusing.
Is it possible to do the references traversals to give "full" path for the files?
This feature could also be implemented in psort.
@Onager
Copy link
Contributor

Onager commented Aug 1, 2018

Yes, this is a known issue, and we plan to solve this at some point using MFT path hints, see #316

I'm going to close this issue out, but know this is definitely something we want to do.

@Onager Onager closed this as completed Aug 1, 2018
@Onager Onager self-assigned this Aug 1, 2018
@Onager Onager added enhancement New or improved functionality duplicate Duplicate of another issue labels Aug 1, 2018
@joachimmetz
Copy link
Member

Is it possible to do the references traversals to give "full" path for the files?

Reconstruction paths from MFT does not necessary yield a single full path. These should be considered more like "full path hints".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Onager Onager

Labels
duplicate Duplicate of another issue enhancement New or improved functionality
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@Onager @joachimmetz @MariasStory