On Tue, Oct 31, 2017 at 2:14 PM, Paul Hammant <paul_at_hammant.org> wrote:
> Consider using Git-subversion.
> 1. git svn clone https://svn.code.sf.net/p/moritz/Archive_SVN/
> 2. edits, git-add, git-commit (all offine) as usual
> 3. git svn dcommit # does the push back to subversion (must be online)
> 4. git svn rebase # is effectively the checkout you're more familar with,
> BUT brings all history so that you can see it while you're offline with
> git-log (etc) operations.
> There are better tutorial elsewhere, but this is a super solid workflow
> for your use case I think.
I was going to suggest the same thing, though given the desired workflow
and the need to work offline it really seems like you ought to just be
using Git. Is there a reason you are hosting a new open source project at
SourceForge as opposed to GitHub? It really is not clear why you want to
use SVN as it is not a good fit for the needs you have described.
Received on 2017-10-31 19:58:51 CET