Avram Lubkin <av...@rockhopper.net> writes: > There are lot of paths, but I wouldn't have expected that to slow it > down. Good catch! > > I'll just run *git log --no-merges --right-only --cherry-pick > --since='2 months ago' some_tag..origin/master* and then run *git log > --since='2 months ago' origin/master -- path1, path2, ...*using the > output of the second to filter the output of the first. > > Is there something else happening when a path is specified with > *--cherry-pick*,
I don't know about the internals. The docs say --cherry-pick omits commits with the same changes as some other commit. I guess it helps filtering out cherry-picks which eventually also got merged and therefore would appear twice (though with different sha1s). > or can the path checking be moved so this is better optimized? Also not sure. I wonder why the path checking is actually important for your case. Bye, Tassilo -- 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/87ednpn5by.fsf%40gnu.org.
