5000 USD seems high to me as well for a student and you don't know what his girlfiend does. It does not really matter how high that amount as long it can cover unexpected expenses.
When I was a student, I made sure I always had at least 1000 EUR on my account, basically treating the 1000 as 0. I cannot remember ever running into debt this way.
That's interesting. Working in an organisation that switched from Gerrit to Github, I saw a decline in commit message quality. Some people will just leave whatever is filled into the textbox by GitHub. In addition, there is no way for others to review the commit message this way.
"Danish, Swedish, Norwegian, Icelandic, Faroese, Hungarian, German, Dutch, and French all have three-form systems. Swedish and Danish have ja, jo, and nej. Norwegian has ja, jo/jau, and nei. Icelandic has já, jú and nei. Faroese has ja, jú and nei. Hungarian has igen, de, and nem. German has ja, doch, and nein. Dutch has ja, jawel, and nee. French has oui, si, and non."
It really got worse. In the past years (always the same IP, good reputation, DKIM), I had a few mails land in the spam folder of gmail users, but it did not happen very often.
This week I encountered the following situation the first time:
1. I received an email from a Google apps (or whatever it is called) user. My response to that email landed in the spam folder.
2. I exchanged one or two mails more with another person in the same organisation without problems.
3. Suddenly my response got rejected. I tried sending via various means such as via Thunderbird, via mobile on 4G, via mobile on Wi-Fi, changing the content slightly... No chance. My email got rejected. In the I ended up calling the person from number 1 on his mobile to get the second person's mobile number...
Needless to say, I have been less than pleased.
Person 1 was very surprised about their spam filter misbehaving, but at least I can now offer an excuse by pointing to this blog post...
Git has a mechanism to declare two commits equal and replace one with the other: man git-replace
This comes at the cost of having intentionally multiple histories and is not well-suited for complicate cases, but for the common case of "we want to stitch this old CVS-history to this commit", it does a good job.
Usability-wise, replace refs are not cloned automatically and some web-based tools lack support for it.
You can also use the 'magic empty tree object' to make your repo more amenable to joining disparate histories of other trees. It requires both the source and destination repo to abide by this practice, but I do this on all of my repos...
Immediately after `git init`, do `git commit --allow-empty -m"initial empty commit"`. Now you have an empty commit, and any other repo which has this empty commit has some history in common with your repo.
The SHA-1 hash is well-known and there are plenty of articles you can find about it, if you search for 4b825dc642cb6eb9a060e54bf8d69288fbee4904
I'm not sure this helps for projects which have a shared development history, but not a shared commit history. But within an organization, where you have projects which may split and/or merge, it can help to bridge some gaps.
I think the payoff is for merging unrelated histories, that you can then rebase one history on the other, and present a new unified history.
Is the really only reason why people do this, so that you can rewrite your initial working commit in a rebase? I think that might be it. (You can't easily rewrite the initial commit with a rebase.)
