I inherited some code that uses *git log --no-merges --right-only --cherry-pick --since='2 months ago' some_tag..origin/master -- path1, path2, ...* as an initial step in determining commits that are missing from some_tag. The main problem is it's slow for a large repo and there is no status.
I can use *git log --since='2 months ago' origin/master -- path1, path2, ...* to get all the commits added for those paths in the specified time, which is fast. Then I'd like to spawn multiple threads to then check the commits individually, but I'm not sure what the equivalent would be for a single commit. I did try comparing *git patch-id --stable* values for all commits within the window and that caught many, but not all, of the commits the original method caught. The ultimate goal is to determine which upstream commits haven't been added to downstream refs. Is there any way to parallelize this internally or externally? -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/git-users/94ce75b2-afd0-4aa2-85a8-8a8872a56ed3n%40googlegroups.com.
