Guten Tag Matt Sicker, am Freitag, 17. März 2017 um 18:27 schrieben Sie: > You can also add > GitHub as an additional remote in your own git clone so that you can > pull directly from github, merge, then push directly to git-wip-us. > GitHub will see the merge commit and will automatically close the > PR.
Thanks a lot for your explanation, Matt. That's basically something like the following, especially beginning with step 5, correct? https://help.github.com/articles/checking-out-pull-requests-locally/#modifying-an-inactive-pull-request-locally That sounds a bit easier than passing patch files around like for SVN and I'm already using an upstream-setup for some GitHub-forked repos already. So with log4cxx, Apache would simply be default/upstream, GitHub a remote downstream set up like upstream in other cases and everything else should be what I'm already doing sometimes... https://help.github.com/articles/configuring-a-remote-for-a-fork/ That sounds preferable over sticking with SVN. Do you see any problems with the names, because the log4cxx-GIT-mirror already exists and there's a repo in GitHub already? That repo has PRs attached already, would be cool if it could simply be updated to current SVN-repo status. Mit freundlichen Grüßen, Thorsten Schöning -- Thorsten Schöning E-Mail: thorsten.schoen...@am-soft.de AM-SoFT IT-Systeme http://www.AM-SoFT.de/ Telefon...........05151- 9468- 55 Fax...............05151- 9468- 88 Mobil..............0178-8 9468- 04 AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow
