**** BEGIN LOGGING AT Sat Apr 07 03:00:00 2018
Apr 07 19:06:39 <sicelo> turns out there's an easy workaround to update one's "fork" (or copy) to match the source repo on Github
Apr 07 19:08:00 <sicelo> that's using the "compare" tool, and swap the base and head repos .. only annoyance is that it creates an extra commit, but merges/updates everything else perfectly
Apr 07 20:19:43 <enyc> sicelo: fun =)
Apr 07 21:09:53 <Maxdamantus> sicelo: yeah, that's effectively what I did with my pull request to myself.
Apr 07 21:10:05 <Maxdamantus> sicelo: but good to know that I can do it without making an actual pull request.
Apr 07 21:10:40 <sicelo> it is a pull request, and that's why it counts as a commit :(
Apr 07 21:10:58 <Maxdamantus> (I just force-updated the branch through the normal git client afterwards, which didn't involve uploading any objects since they were already in the repo)
Apr 07 21:11:02 <Maxdamantus> Ah right.
Apr 07 21:12:14 <sicelo> i just re-read your earlier reply, and yes, you were right. i didn't understand it by then
Apr 07 21:45:19 <sicelo> 22:34  * DocScrutinizer05 is used to sending patch emails ;-)  <<<< seems git is happy to work that way too. (`git format-patch` for example, and `git apply`)
Apr 07 21:51:34 <Maxdamantus> Yeah, and aiui a lot of linux development is done using patches.
Apr 07 21:52:13 <Maxdamantus> where people just share patches to topic-specific mailing lists, and maintainers apply them to their branches, which are eventually merged higher up.
**** ENDING LOGGING AT Sun Apr 08 03:00:02 2018