You might find git to be more flexible than svn.

gdjacobs wrote:

You might find git to be more flexible than svn.

Do you suggest that I set up and maintain a Git repository with a mirror of the official DOSBox SVN?

I don't have a clue about SVN, but since git was mentioned, yes it's super-super easy to create diff files/patches with git. Easy as a 3-word command with the output redirected to a file. I used to hate git but hey, I got old and sane 😀

you can use svn add filename
to add it. You don't need write access to do that.
then svn diff will include that file "filename" as well.

Thank you, Qbix.

1svn checkout svn://svn.code.sf.net/p/dosbox/code-0/dosbox/trunk dosbox-code-0
2cd dosbox-code-0
3echo hi >test.txt
4svn add test.txt
5svn diff --ignore-properties

or use as last line

1svn diff --patch-compatible

both will give

1Index: test.txt
2===================================================================
3--- test.txt    (nonexistent)
4+++ test.txt    (working copy)
5@@ -0,0 +1 @@
6+hi

of course you need to redirect the output to a file to save it.

Ant_222 wrote:

Do you suggest that I set up and maintain a Git repository with a mirror of the official DOSBox SVN?

You can use the subversion bridging tool to pull into a local GIT repository which then gives you the full GIT toolset on your local copy. If you're only doing small stuff, it might not be worth it. If you're making substantial changes to the tree and merging them back or if it provides a way of keeping things organized, GIT could be a very powerful tool for you.

gdjacobs, Right now I need to simplify relatively small changes, so Qbix's advice is the right next step for me. As far as I know, SVN offers the same fundamental functionality as GIT, i.e.: checkout, commit, branch, merge, diff; and whereas DOXBox is hosted in SVN I shall use that unless or until I meet with such incoveniences as GIT solves considerably better than SVN. I am on the path of least resistance and try do to the simplest thing that works.

Again, the big difference is that with GIT the functionality is available by design for your local work as well as on the central server, and GIT is better at merging changes between different source trees (as that's what it was designed for).

The good news is that you're not locked into any particular tool. SVN is mature and works quite well within it's scope, but if you begin running into it's limits, you've got a wealth of options available to you.

I use quilt. It's quite sophisticated, if linux only.

Yes. Andrew Morton is a clever guy.