Allow ubireader_list_files to recursively list files under a path#118
Conversation
74e2c7b to
dee92a9
Compare
b6ad0e6 to
e2f6845
Compare
|
There are 2 flags and features added in this MR:
Both of them are passed down the functions, adding to their complexity. At least the recursive flag should be handled as a separate path - this is most visible in I think this recursive listing should be implemented in a separate function, that handles the recursion: |
c096c9c to
bed815d
Compare
|
@e3krisztian, I don't really see your vision on this. I went ahead and made some changes, but I fail to see how this is an improvement. |
|
@scootermon I am very sorry for both being extremely slow and late with the review and answering and also to cause confusion with my comment. This is how I was thinking about it (patch is based on your original change): 905445f (https://github.com/onekey-sec/ubi_reader/commits/list-recursive-suggestion/) This is not tested, and does not include your recent changes in the history (rebase and improvement attempts). Actually, you had a very similar attempt in c096c9c, but made the split on I think it is important for |
|
Thanks for following up on this, @e3krisztian.
EDIT: Realized that the feature is still being used by the print_dent_recursive function so it makes sense to keep it.
That's fair, I keep having to fight the urge to format the code. I went ahead and "merged" your suggestion in 580dd88. |
bed815d to
580dd88
Compare
e3krisztian
left a comment
There was a problem hiding this comment.
@scootermon Thanks for the update!
I am happy with the code, and it can be merged - if you are also happy with it, could you squash the commits?
cfa205b to
de90c5f
Compare
The default output of ubireader_list_files remains the same, but when you add '--recursive' it will recursively list all the inodes under the listpath. It then also displays the absolute path to the files instead of just the name. Co-authored-by: Krisztián Fekete <1246751+e3krisztian@users.noreply.github.com>
de90c5f to
34889a9
Compare
|
@scootermon thank you for your contribution! |
This is based on top of #117, but I'm happy to rebase it.