Jukka Zitting wrote on Thu, May 24, 2012 at 13:39:48 +0200: > The GitHub pull request notification you saw on dev@subversion, is a > result of our work to better integrate GitHub workflows with those at > Apache. The idea here is to send the issue to dev@ from where the > project community can deal with it in whichever way it prefers, for > example by telling the contributor to use other channels, by filing a > bug for the issue, or by simply directly applying the contributed > patch. > > Currently the pull request notification doesn't come with a full diff, > but we can add that if desired.
Subversion has a specific process for incoming patches: we expect patches to contain at least a log message (written according to <http://subversion.apache.org/docs/community-guide/conventions#log-messages>) and a unidiff. We also expect to be discussed --- this can take the form of a "cover letter" in the submission, or of a normal dev@ thread before diving into the code. Can the git.a.o tooling support our workflow?
