On 07 Dec 2023, at 14:38, Jason Yundt <jason@jasonyundt.email> wrote:
> Here’s the questions that I still have: > > • With Git, there’s multiple different ways of sending your changes > upstream (pull requests, git-request-pull and git-send-email). Are there > multiple ways of doing it with Subversion or do you always just send > emails with patches attached? Ultimately, the common thing in all of these different version control systems is the patch file, the file that says what lines are being added and what lines are being taken away. As long as you get the patch file cleanly to your target audience in some form, you’re done. That could be by email, posting to a mailing list, etc. The idea of a pull request is when someone puts a user experience around handling the patch file. Github is probably the best example of this, thought the idea has been copied by everyone else. The Apache SVN repos are all mirrored at Github, meaning that you could use the Github pull request workflow to propose changes to SVN repos. Here is an example of a pull request made to the subversion project: https://github.com/apache/subversion/pull/23 > • I followed my own instructions to create an example patch for > <https://svn.apache.org/repos/asf/subversion/trunk/>, and I attached it > to this email. Does it look like I created the patch correctly? > > [1]: <https://subversion.apache.org/docs/community-guide/general.html#patches> > <example.patch> Example is perfect. Regards, Graham —
