61–68 of 68 posts
and in the only case this would work, i.e. nobody has that commit yet, you could just have commited as that person. nothing new or interesting.
now, github being garbage and not accounting for PGP signatures, now this is something else.
Earlier quoted context omitted.
Best in what sense? Bitbucket does everything Github does, plus gives free private repos. GitHub is just more widely used.
Bitbucket crashes minimal browsers like Surf and github doesn't. So, in that regard, Github is better.
Earlier quoted context omitted.
You mean besides developing and operating one of the best services on the web?
Best in what sense? Bitbucket does everything Github does, plus gives free private repos. GitHub is just more widely used.
on a slow connection, this allows you to work on or inspect repos that are too large to git clone (one of the few major complaints i have with git itself)
It's been my experience, especially in the startup scene where business requirements change often, that `git blame` rarely shows you what you want. Files get renamed, moved, re-indented, etc, frequently. I wrote a tutorial on a more effective (at least for me) solution to find the true author of a change: http://blog.andrewray.me/a-better-git-blame/
Blame follows renames in most cases (unless you're doing something like creating a new file with the same name as the renamed one in the same commit), and you can use the -w flag to ignore whitespace changes.
Earlier quoted context omitted.
You mean besides developing and operating one of the best services on the web?
Best in what sense? Bitbucket does everything Github does, plus gives free private repos. GitHub is just more widely used.
Earlier quoted context omitted.
Worrying and potentially libelous. Some countries (e.g. UK) have strict libel law, and by using this you could get Github in trouble for publishing libelous material. Of course, this has always been possible with git.
Though since GitHub does not have an office in the UK and in the US is protected from foreign defamation judgements under the SPEECH Act, it probably doesn't have much to worry about.
Earlier quoted context omitted.
Nice tutorial, but aren't you aware that "git blame -w" ignores whitespace changes? git blame also always follows renames. git's rename detection isn't foolproof (if I edit and rename A.cpp to A-star.cpp at the same time as adding a new A.cpp file it won't detect it), however there are two more blame options for that: -C to follow lines copied between files, and -M to follow lines moved within a file. Unfortunately,…
I would love to be able to use left and right to skip quickly through revisions when viewing a blame, do you know anything for that?
tig (a curses-based git interface) fits the bill, though it can be quite confusing (too many keybindings). "tig blame -w " to view a blame (-w to ignore whitespace), and then you can press , on a line to recompute the blame using the parent of that commit, while moving to the ancestor of that line (but tracking the line frequently doesn't work). And I remember that tortoisesvn was fairly nice for viewing blames, IIRC you can move through history inside it with some clicking around, and the tortoisegit interface appears to be largely the same: https://tortoisegit.org/docs/tortoisegit/tgit-dug-blame.html Windows only however.