-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
git-effort on a old codebase #326
Comments
You be a useful flag to have AFAIK, are you interested in doing a PR? |
Sorry, I do not have the time to contribute :( At least not in the near future. |
[RFC] effort: Allow sending options to log. Fix #326
Thank you! I will test it soon. |
Yes, please :) If there are a lot of files in your repo you should try specifying the ones you care about. This can speed up the command by orders of magnitude. |
@nicolaiskogheim thank you! The problem is not the speed, this is not a command I run often, but the relevance. If I land on an old project, I am interested where most of the edits have gone to in the past 6 months. I really don't care that 5 years ago, a file got 1000 commits and nobody touched it since. This tool is great! Thank you again! |
effort: documentation for git effort --since #326
[RFC] effort: Allow sending options to log. Fix tj#326
effort: documentation for git effort --since tj#326
Hi,
git effort is an awesome tool! :D I am running it on the LibreOffice codebase and I started yesterday and it is still running. The purpose of running it is to find what are the most actively commited files so I can figure out what are the most important files that I need to understand. The problem is the fact that it takes TOOO long.
A proposed solution is to pass as an argument an interval for what commits to check since the latest commits are more relevant. Passing
--since
togit log
seems like a simple sollution.Do you think this is possible/useful?
Thank you!
The text was updated successfully, but these errors were encountered: