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
Put log--detailed back #47
Comments
Yeah, this feature fell out when I redesigned the version-control subsystem. But I understand its importance. Computing the difference between revisions is somewhat expensive now. And most of the time, you probably only care about certain revisions. So showing the diff for every revision in the log seems like overkill. My plan is to extend the $ pinto diff 3465afbe f3876ade What do you think of that? |
The ability to search the changes is very important. Often I'm searching through the log to see when I upgraded or downgraded a given distribution, so I don't already know the revision numbers. |
Understood. We'll just have to see how expensive it is. I've added this to |
An extra data point about my use of Pinto. My automated import of modules had a message like "Matching existing installed rpm version" with no mention of what was being added. I figured that was easy to get what was being added from the pinto log. |
Makes perfect sense. |
Pinto 0.097_01 will ship to CPAN as soon as PAUSE is running again. Note this is a developer version for now. The There have been several other enhancements to diff reporting throughout Pinto. See the Changes log for details. |
Pinto 0.098 has shipped to CPAN with this feature, so I'm closing this issue out. |
The new pinto log only displays the revision, date, author and message. There doesn't appear to be any way to see what's actually changed. The
--detailed
flag used to provide this critical functionality.Could we have it back?
The text was updated successfully, but these errors were encountered: