latest 20 messages by Peng

+ [2019-03-23T05:21:30Z] Peng 1.) Don't spam. 2.) That's vague.
+ [2019-03-17T17:00:14Z] Peng You can push to update them.
+ [2017-07-07T09:06:37Z] Peng git commit --amend
+ [2017-07-07T09:06:34Z] Peng The message is part of the commit. Modifying it would change the ID and so forth, so you'd be rewriting history.
+ [2017-07-07T09:06:11Z] Peng Have you already pushed it?
+ [2017-03-25T04:56:15Z] Peng If not, mention the issue in a comment on the pull request, and they'll still be partly linked.
+ [2017-03-25T04:55:37Z] Peng File a pull request. It will automatically be associated with the issue if any of the commit messages contain "fixes #1234" or a few different similar strings.
+ [2017-02-12T01:54:24Z] Peng That's literally all it means. But they're commonly associated with gpg/PGP
+ [2017-02-12T01:53:30Z] Peng ASCII text file.
+ [2017-02-11T21:41:57Z] Peng That sounds copyright-infringey
+ [2016-12-19T00:20:10Z] Peng k
+ [2016-12-19T00:20:09Z] Peng It's been a wee
+ [2016-12-19T00:19:58Z] Peng As long as you don't git rebase them out of the history to "steal" the credit, i don't think it's unethical?
+ [2016-12-09T15:32:06Z] Peng Now and forever. So you don't have to decide what to do now, though it might be more convenient,
+ [2016-12-09T15:31:54Z] Peng As long as you don't overuse "git rebase" and fry your history, you can always go back and read "git log" and find a good revision and create a new v0.1 branch or tag.
+ [2016-12-09T15:30:02Z] Peng Ah. You said that. Yes, a branch or a tag.
+ [2016-12-09T15:29:42Z] Peng Have a v0.1 branch and/or tag, push it to GitHub, don't delete it.
+ [2016-12-09T15:29:10Z] Peng among other things
+ [2016-10-27T20:07:53Z] Peng https://github.com/blog/2228-simpler-github-pages-publishing
+ [2016-10-27T20:07:03Z] Peng I mean, the latter one does. gh-pages or master.