id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
16729	No trunk branch for GitHub plugins	Don-vip	floscher	"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):

{{{
Commit failed (details follow):
Unexpected server error 500 'Internal Server Error' on
 '/JOSM/pt_assistant/!svn/wrk/7dffa700-c16c-324f-a02f-f3f064ba81a2/branches/trunk/.classpath'
}}}

Can you please rename the few ""trunk"" branches to master so we get back a clean situation?"	task	closed	normal		Core		fixed	git svn github trunk master