HN Explorer

12 comments

[ 3.5 ms ] story [ 58.6 ms ] thread
nasretdinov
The only downside of this script is that it changes commit hashes, so you actually can only blame someone else if you force-push or just showing blame on your computer. It would be nice if it could be done without changing the commit SHAs.
ditsuke
That could've been possible if Git didn't use commit metadata hashes, (un)fortunately it's smart enough to do that.
proto_lambda
The whole point of commit hashes is that you can't do that, so no, being able to change history undetected would not be nice at all.
aflag
Initially I thought it would show all changes to a file that were made by someone other than the person running the command. So, for instance, if there's a line I changed recently, it would go down history further to find the original author.
Tyr42
That's what I was looking for too. Would be useful.
aae42
This is why I sign my commits... It's also easy these days to do it with an SSH key
saagarjha
It's actually a pretty convenient script to use locally when doing repository manipulation, for example when you're cherry-picking other people's commit via patch and want to attribute it to them.
ahrzb
But changing commit author is quite easy with git, just do: ‘git commit -a —author “<name+email>”’
saagarjha
I often need to change the author on commits that aren't the topmost one.
rurban
Then do it via rebase -i and e. I do that constantly,
saagarjha
Yeah, but that's more annoying ;)