If anyone (with commit access) is interested, here's how to use git to work distributed/offline, then commit your work back up to the subversion repository. I used a branch, even though this was a trivial commit.
(1.3_jfkw) $ git checkout trunk (9b24d10...) $ git checkout -b 1.3_INSTALL Switched to a new branch "1.3_INSTALL" (edit INSTALL...) (1.3_INSTALL) $ git add INSTALL (1.3_INSTALL) $ git commit -m 'minor INSTALL cleanup for test commit' Created commit 5b460f6: minor INSTALL cleanup for test commit 1 files changed, 11 insertions(+), 9 deletions(-) (1.3_INSTALL) $ git svn rebase Current branch 1.3_INSTALL is up to date. (1.3_INSTALL) $ git svn dcommit Committing to https://ledger-smb.svn.sourceforge.net/svnroot/ledger-smb/trunk ... Authentication realm: <https://ledger-smb.svn.sourceforge.net:443> SourceForge Subversion area Username: jfkw Password for 'jfkw': M INSTALL Committed r2311 M INSTALL r2311 = 588c85da34100616c782ac4c10bfa78573d427e6 (trunk) No changes between current HEAD and refs/remotes/trunk Resetting to the latest refs/remotes/trunk I'd like to add and maintain a README.git, if no one objects. ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Ledger-smb-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ledger-smb-devel
