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.

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

Obtaining Relevant Blob/Filename to Project (c2b, b2f, c2f) #36

Open
k----n opened this issue Sep 7, 2021 · 3 comments
Open

Obtaining Relevant Blob/Filename to Project (c2b, b2f, c2f) #36

k----n opened this issue Sep 7, 2021 · 3 comments

Comments

@k----n
Copy link
Contributor

k----n commented Sep 7, 2021

Right now for me to obtain the relevant file of a project, I first use c2b and then b2f to try to match with c2f.

Is there a more efficient way of doing this?

@audrism
Copy link
Collaborator

audrism commented Sep 7, 2021

gz/c2fbbFullT{0..127}.s has c;f;b;ob, but the random lookup tables are not produced. Depending on the number of use cases they may be a good candidate for the next lookup table.

@k----n
Copy link
Contributor Author

k----n commented Sep 7, 2021

When analyzing at a repository level, it's useful to know the path and the blob associated with the path.

Without the random lookup tables, I don't think zcat the maps makes lookup any faster than just combining c2b, b2f, c2f?

@audrism
Copy link
Collaborator

audrism commented Sep 8, 2021

Another a bit slower way is to use c2b and the showCnt tree (there is recursive option) catching the blobs created by that c.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants