| 1 | | I see more and more plugins using a "trunk" git branch on GitHub. This is not correct. GitHub bridge maps "trunk" [https://help.github.com/articles/support-for-subversion-clients/ to the Git HEAD branch], which is usually master, and it seems it chokes if the branch is also called trunk, causing many svn errors during update or commit (right now I can't commit on pt_assistant because of this). |
| | 1 | I see more and more plugins using a "trunk" git branch on GitHub. This is not correct. GitHub bridge maps "trunk" [https://help.github.com/articles/support-for-subversion-clients/ to the Git HEAD branch], which is usually master, and it seems it chokes if the branch is also called trunk, causing many svn errors during update or commit (right now I can't commit on pt_assistant because of this): |
| | 2 | |
| | 3 | {{{ |
| | 4 | Commit failed (details follow): |
| | 5 | Unexpected server error 500 'Internal Server Error' on |
| | 6 | '/JOSM/pt_assistant/!svn/wrk/7dffa700-c16c-324f-a02f-f3f064ba81a2/branches/trunk/.classpath' |
| | 7 | }}} |
