Hi Regina, On Sat, May 19, 2012 at 08:07:21PM +0200, Regina Henschel wrote: > Hi Dennis, > > Dennis E. Hamilton schrieb: > >OK, I see. Ariel's advice is appropriate if you are comfortable with > >GIT and like the compactness. However, it is only good for > >non-committer activities, such as seeing if you can build from > >source, etc. > > > >(By the way, with the latest SVN and especially with TortoiseSVN, I > >don't know that there is much difference in the size for working > >copies, and you can be very selective with what you check out and > >keep updated.) > > I had bad experience with TortoiseSVN. It puts itself in a way into > the Windows explorer, that the explorer becomes so slow, that it was > unusable. Therefore I uninstalled TortoiseSVN. For making patches > that other push, I did not need it.
In general, Subversion sucks (I don't say it loud, as it is an Apache project ;) ). > > > >However, GIT is not supported for what committers do on Apache > >OpenOffice. No pushing changes. The GIT view of the Apache > >OpenOffice SVN repository is read-only. > > Command 'git svn dcommit' should push the changes. But I don't know > whether the commit message will be transfered Yes, it will be transfered. > too or if I need something in addition. And I'm afraid of disturbing > something, otherwise I would simple try it. Before really committing the changes to the SVN repo, you can always test what will be committed: git svn dcommit --dry-run Then commit: git svn dcommit As long as you didn't yet run "git svn dcommit" you can do everything you can do with git (combine commits, change commit message, etc.), you have all the power of working with git :) Regards -- Ariel Constenla-Haile La Plata, Argentina
pgpHqzoiO9qHm.pgp
Description: PGP signature
