Return-Path: X-Original-To: apmail-incubator-ooo-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-ooo-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E0A49C0DD for ; Sat, 19 May 2012 18:24:44 +0000 (UTC) Received: (qmail 28755 invoked by uid 500); 19 May 2012 18:24:44 -0000 Delivered-To: apmail-incubator-ooo-dev-archive@incubator.apache.org Received: (qmail 28684 invoked by uid 500); 19 May 2012 18:24:44 -0000 Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ooo-dev@incubator.apache.org Delivered-To: mailing list ooo-dev@incubator.apache.org Received: (qmail 28674 invoked by uid 99); 19 May 2012 18:24:44 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 19 May 2012 18:24:44 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of dennis.hamilton@acm.org designates 216.119.133.2 as permitted sender) Received: from [216.119.133.2] (HELO a2s42.a2hosting.com) (216.119.133.2) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 19 May 2012 18:24:35 +0000 Received: from 97-126-115-227.tukw.qwest.net ([97.126.115.227] helo=Astraendo) by a2s42.a2hosting.com with esmtpa (Exim 4.69) (envelope-from ) id 1SVoK6-00327W-FS for ooo-dev@incubator.apache.org; Sat, 19 May 2012 14:24:14 -0400 Reply-To: From: "Dennis E. Hamilton" To: References: <4FB7B0A3.5060502@t-online.de> <009f01cd35d9$cb894a00$629bde00$@acm.org> <4FB7C987.4090804@t-online.de> <000601cd35e4$c2ef9830$48cec890$@acm.org> <4FB7E159.5070105@t-online.de> In-Reply-To: <4FB7E159.5070105@t-online.de> Subject: RE: Need guide for my first 'push' Date: Sat, 19 May 2012 11:24:22 -0700 Organization: NuovoDoc Message-ID: <002601cd35ec$9d730fd0$d8592f70$@acm.org> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQHaSCTi3r73NYRQT8EjAMU6OqkCcQGrcmJ4AzCtc4QBeqKPzQIPcIhIlnQWjgA= Content-Language: en-us X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - a2s42.a2hosting.com X-AntiAbuse: Original Domain - incubator.apache.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - acm.org 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:rb.henschel@t-online.de]=20 Sent: Saturday, May 19, 2012 11:07 To: ooo-dev@incubator.apache.org 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=20 Windows explorer, that the explorer becomes so slow, that it was=20 unusable. Therefore I uninstalled TortoiseSVN. For making patches that=20 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=20 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=20 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=20 have attached it to https://issues.apache.org/ooo/show_bug.cgi?id=3D3582 Kind regards Regina