+ [2016-02-25T18:08:08Z] Overand (Ignore my earlier question. Added the SomeAwesomePatch as a remote, fetched, and cherry-picked, seems to ahve worked fine
+ [2016-02-25T19:32:55Z] blueyed The testmon issue might be fixed with https://github.com/tarpas/pytest-testmon/pull/35 - is that sane?
+ [2016-02-25T19:42:06Z] blackwind_123 hi how to create permalinks in gist gistuhb quickly...????
+ [2016-02-25T23:17:54Z] inflames there is a project that has fallen out of sync with the project it was forked from and subsequently basically abandoned, i rewrote the fork via the main project and am debating giving it the same name as his in an attempt to replace his, even if it's a lot more work, do you guys think out of respect for the original fork i should fork his, make the changes and issue a pull request to him? (the changes would not really merge
+ [2016-02-25T23:17:55Z] inflames into his project, it's basically a complete rewrite of his)

message no. 124984

Posted by Overand in #github at 2016-02-25T17:06:54Z

...wow, homerow error. Is there a "proper" way for me to facilitate the merging of someone's fork of an *old* fork with the current "master" project?
+ [2016-02-26T00:10:39Z] technicalpickles inflames: that is a tough one. I take it the main project isn't maintained anymore?
+ [2016-02-26T00:11:14Z] technicalpickles that is a nice consideration to do a pull request to the fork, but at the same time, I'm not sure how I would personally feel about getting a PR to entirely rewrite something if I was on the receiving end :)
+ [2016-02-26T00:12:45Z] technicalpickles I think I would choose a new name, and give credit in the README
+ [2016-02-26T00:25:40Z] linuxmodder markdown question: if I have a code block and want comments outside of it the ```bash should be AFTER the comment correct?
+ [2016-02-26T00:26:11Z] linuxmodder i.e. This statically links these bits \n ```bash \n {code block }