Hi,
Patrick Cardona wrote:
I know how to fork a git repo and to submit a pull request to the owner.
Cool! that is a GitHub thing though, constructed on top of git.
I would like to be able to do the same for some subversion repo,
namely to contribute to translations and help files of GNUstep
applications.
Cool. Most apps are not setup to handle translations though, so that
should be improved. It is on my working list for those which are under
my control.
- I know how to check out and creating a branch within svn.
You can create a branch and work on your own purpose, although without
GitHub no PR.
It depends on how the repository was set up in the "dark ages".
Some project are a "big thing", so if you branch, you branch everything,
not just the single application. Others are intermediate... it is a bit
a mess. It would be nice to rectify this eventually, but it is important
not to loose revision history.
I don't know if the structuring of "libs" vs "apps" for example is
feasible in SVN.
in GIT subrepositories are needed, GitHub supports them (but everything
is flat, like GNUstep is setup currently) or need manual creation like
in savannah, but would be flat anyway.
- Because I have not the permissions to merge or to commit then to
the trunk HEAD - what I understand - I would like to know how I could
submit some minor changes: I tried first 'svn diff' to create a patch,
but not all the changes were handled.
- I thought I could also create a whole tarball of my branch and send
it by mail: is it a good matter to do that?
That is a little bit inconvenient, because it would send your
"repository" not just your files.
To sumarize, what are the good practices to contribute on subversion
repo like on Savannah?
Easiest way for contributions is to generate patches and share them. Old
fashioned, but works. There are projects (e.g. HURD or OpenBSD) who rely
on that for review, patch generation and emailing can be even automatized
Now if you ask me why a "svn diff" contains only differences to existing
files and not new files, you catch me unprepared.
According to:
https://svnbook.red-bean.com/en/1.8/svn.ref.svn.html#svn.ref.svn.sw.no_diff_added
"the --no-diff-added" should prevent from printing differences from
files compared to an empty one, which is exactly what we need for a
patch containing both changes and additions!
Just attach/zip the new file separately for the time being.
Ideas?
(It would work in any case for text files only, also in git we see the
limitation that binary patches are usually not extracted from the repository
Riccardo
