I see that you submitted the patch. There is no way to do commits to Apache OpenOffice via GIT.
I had not encountered that problem with Tortoise SVN on my Windows XP machine. Most of my working copies are in shared folders on a home server, and not even that is a problem. There have been serious performance improvements. You might try it again. You can run the command-line SVN, of course. - Dennis -----Original Message----- From: Regina Henschel [mailto:[email protected]] Sent: Saturday, May 19, 2012 11:07 To: [email protected] Subject: Re: Need guide for my first 'push' 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. > > 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 too or if I need something in addition. And I'm afraid of disturbing something, otherwise I would simple try it. Perhaps I wait, whether Ariel has an answer, for he guide me to git-svn. Making the patch available for review before pushing is a good idea. I have attached it to https://issues.apache.org/ooo/show_bug.cgi?id=3582 Kind regards Regina
