Hi, I see more and more patches being provided from a GIT-fork of our
projects.To me it's still a mystery how to translate them to usable
svn-patches.I think it's an illusion that we can force the contributors to
provide only svn-patches, so I'd like someone to write a page how we can
transform such patches. The following things should be included:For
contributors: - fork from the trunk, not from the tag. (I think there's some
here work for the maven-team too to include this in one of their reports. Right
now I'm thinking on the issue-management page, since it has enough space and is
closely related. Otherwise the source-repository page)- how to make the patch
easy to apply for mojo-developers (root of plugin, generate a svn-patch (?)).
For the mojo-team:- how to transform a patch from GIT Has anyone the knowledge
to write this? thanks, Robert
