Conversation
I got annoyed by seeing all those `TLSv1.2 (IN), TLS header, Unknown (23):` in the `-v` trace. So this fix is now printing: ``` * TLSv1.2 (OUT), TLS header, Supplemental data (23): ```
|
Effin github editor. What is leaving trailing white-space good for?
|
Trailing whitespace removed. Okay to Rebase and merge? |
|
I advice against using the UI/button for git operations because it is much harder to figure out exactly what happens and that the commit message etc is done correctly. For example, your commit message could benefit from these edits:
It is much better to squash the commit locally, edit the commit message to be fine, then merge that into the master branch and push from there to "origin/master". |
|
Most of these git-terms are alien to me. And it's too much hassle to clone, edit, push. Should be easier to use the Web-UI directly. |
|
Most of these git-terms are alien to me. And it's too much hassle to clone, edit, push. Should be easier to use the Web-UI directly.
I can push it for you with the edits requested below if you would prefer that.
|
I wouldn't mind that either. But I also want our commits and commits messages to be as good as possible, and I don't think github helps us good enough with that. |
Done. |
3 participants
I got annoyed by seeing all those
TLSv1.2 (IN), TLS header, Unknown (23):in the-vtrace.So this fix is now printing:
I hope this is a proper fix.