3 ms·
I had the same skeptical question in my head while reading the landing page / ad. But, I will say I super miss P4's 'timeline'. I haven't used Perforce tools f
by dahart 11y ago
I had the same skeptical question in my head while reading the landing page / ad.
But, I will say I super miss P4's 'timeline'. I haven't used Perforce tools for many years now, but last time I did it was way way easier & faster to figure out who wrote a line of code than it is in git today. And overall, the UI was much better then than any git based UI is today. So, it might be hard for them to explain to git users, but personally, I'm open to the possibility they have some value added.
- Tuna-Fish 11y ago> it was way way easier & faster to figure out who wrote a line of code than it is in git today. Don't you have git blame integration in your editor?
- brianwawok 11y agoGit blame will often get the guy who fixed a spelling mistake in a variable, not the guy before him who wrote the code.
- kazinator 11y agoTo continue digging previous history: git blame <sha>^ -- file.c Where <sha> is the hash of the commit where the spelling mistake was made, pulled from the original blame from HEAD. Though I don't use such stuff, I would be surprised if there wasn't IDE support to make this "deeper dig" more of a point and click operation.
- vetrom 11y agoThere is, try `git gui blame`.
- dahart 11y agoI do, and it doesn't hold even 1 candela to P4's timeline. ;)