Re: [PROPOSAL] move repo to Git.

2015-03-25 Thread wolf . halton
-Original Message- From: Jürgen Schmidt [mailto:jogischm...@gmail.com] Sent: Tuesday, February 17, 2015 04:01 To: dev@openoffice.apache.org Subject: Re: [PROPOSAL] move repo to Git. [ ... ] If possible to get a git repo only it make sense. That means we don't have to move any

Re: [PROPOSAL] move repo to Git.

2015-03-08 Thread Marcus
of sending fixes upstream than going the patch creation and submission route. - Dennis -Original Message- From: Jürgen Schmidt [mailto:jogischm...@gmail.com] Sent: Tuesday, February 17, 2015 04:01 To: dev@openoffice.apache.org Subject: Re: [PROPOSAL] move repo to Git. [ ... ] If possible

Re: [PROPOSAL] move repo to Git.

2015-03-08 Thread Marcus
: [PROPOSAL] move repo to Git. [ ... ] If possible to get a git repo only it make sense. That means we don't have to move any webpage related stuff into git. Just the pure code is relevant her. +1 for a git repo Juergen

Re: [PROPOSAL] move repo to Git.

2015-03-08 Thread jan i
-friction way of sending fixes upstream than going the patch creation and submission route. - Dennis -Original Message- From: Jürgen Schmidt [mailto:jogischm...@gmail.com] Sent: Tuesday, February 17, 2015 04:01 To: dev@openoffice.apache.org Subject: Re: [PROPOSAL] move repo to Git

Re: [PROPOSAL] move repo to Git.

2015-03-07 Thread wolf . halton
route. - Dennis -Original Message- From: Jürgen Schmidt [mailto:jogischm...@gmail.com] Sent: Tuesday, February 17, 2015 04:01 To: dev@openoffice.apache.org Subject: Re: [PROPOSAL] move repo to Git. [ ... ] If possible to get a git repo only it make sense. That means we don't

RE: [PROPOSAL] move repo to Git.

2015-03-01 Thread Dennis E. Hamilton
. It seems this is a lower-friction way of sending fixes upstream than going the patch creation and submission route. - Dennis -Original Message- From: Jürgen Schmidt [mailto:jogischm...@gmail.com] Sent: Tuesday, February 17, 2015 04:01 To: dev@openoffice.apache.org Subject: Re: [PROPOSAL] move

Re: [PROPOSAL] move repo to Git.

2015-02-18 Thread Yuri Dario
Hi, a bit late... having worked with both svn and git, personally I don't think git it is easier to use. Given how AOO is developed, it seems to me that cloned repos are not necessary, developers are already working on svn repo. -- Bye, Yuri Dario

RE: [PROPOSAL] move repo to Git.

2015-02-18 Thread Dennis E. Hamilton
and how there is no hierarchy of committers, so I haven't dug too far into it. My picture here is therefore rather sketchy. -Original Message- From: Yuri Dario [mailto:mc6...@mclink.it] Sent: Wednesday, February 18, 2015 02:54 To: dev@openoffice.apache.org Subject: Re: [PROPOSAL] move

Re: [PROPOSAL] move repo to Git.

2015-02-17 Thread Jürgen Schmidt
On 16/02/15 19:01, Kay Schenk wrote: I'm just curious about these statements. Have potential new developers remarked on this to you? Since most IDEs support a variety of version control mechanisms, I'm wondering how the suggestion to switch to git might have emerged. But, again, I have

Re: [PROPOSAL] move repo to Git.

2015-02-16 Thread Kay Schenk
On Fri, Feb 13, 2015 at 9:53 AM, jan i j...@apache.org wrote: On 13 February 2015 at 18:13, Kay Schenk kay.sch...@gmail.com wrote: On Fri, Feb 13, 2015 at 3:43 AM, jan i j...@apache.org wrote: Hi. We have now for a while had a readonly Git copy of our svn repo. Should we move

Re: [PROPOSAL] move repo to Git.

2015-02-16 Thread Marcus
Am 02/15/2015 02:19 PM, schrieb Andrea Pescetti: So, from what I can understand, the GIT repository would only replace these three directories: http://svn.apache.org/viewvc/openoffice/trunk/ (which would become the master branch) http://svn.apache.org/viewvc/openoffice/branches/

RE: [PROPOSAL] move repo to Git.

2015-02-16 Thread Dennis E. Hamilton
-- replying in-line to -- From: Kay Schenk [mailto:kay.sch...@gmail.com] Sent: Monday, February 16, 2015 10:01 To: OOo Apache Subject: Re: [PROPOSAL] move repo to Git. [ ... ] I'm just curious about these statements. Have potential new developers remarked on this to you? Since most IDEs

Re: [PROPOSAL] move repo to Git.

2015-02-16 Thread Andrea Pescetti
On 16/02/2015 Kay Schenk wrote: again, I have never used git and it might be the coolest thing ever It does have a reputation for being cool. This is justified in many cases, less justified in others. I know some developers who refuse to work with SVN in principle; true, maybe they would be

Re: [PROPOSAL] move repo to Git.

2015-02-15 Thread Andrea Pescetti
On 13/02/2015 jan i wrote: Should we move to a full git repo, making it easier for new developers to participate (although it is in no way a guarantee, that it will attract new people) by lowering the barrier. (Sorry if you already got this message: I'm experiencing problems and delays with

Re: [PROPOSAL] move repo to Git.

2015-02-15 Thread Andrea Pescetti
Dennis E. Hamilton wrote: OK. Then what is the point of github_team.txt? Vanity only. People will see the Apache badge when looking at your Github profile. So this has little in common with this discussion, which is about two tools (svn and git) both hosted at Apache. Regards, Andrea.

RE: [PROPOSAL] move repo to Git.

2015-02-15 Thread Dennis E. Hamilton
Got it. Sorry for wasting everyone's time. - Dennis -Original Message- From: Andrea Pescetti [mailto:pesce...@apache.org] Sent: Sunday, February 15, 2015 04:49 To: dev@openoffice.apache.org Subject: Re: [PROPOSAL] move repo to Git. Dennis E. Hamilton wrote: OK. Then what

RE: [PROPOSAL] move repo to Git.

2015-02-15 Thread Dennis E. Hamilton
-- replying in-line to -- From: jan i [mailto:j...@apache.org] Sent: Saturday, February 14, 2015 13:36 To: dev; Dennis Hamilton Subject: Re: [PROPOSAL] move repo to Git. On 14 February 2015 at 22:27, Dennis E. Hamilton dennis.hamil...@acm.org wrote: Corinthia has its code tree (not web site

Re: [PROPOSAL] move repo to Git.

2015-02-15 Thread Herbert Duerr
Hi Pedro, I don't currently use git but what I use is not really important: if a move to git were to be considered, it would only make sense if we can rescue the pre-apache history and in particular the Hg CWSs. Most of the open-source history has been preserved. I talked about this in my

Re: [PROPOSAL] move repo to Git.

2015-02-14 Thread Mechtilde
Hello, personally I prefer Git. But this doens't matter Who do the administration of the core code like branch and merge and so on? These persons should get the best free tool being available. Kind regards Mechtilde Stehmann --- ## Apache OpenOffice.org ## Freie Office Suite für Linux,

Re: [PROPOSAL] move repo to Git.

2015-02-14 Thread Dave Fisher
Hi - In SVN you can choose parts of the repository. In Git it is all or none. If we move to GIT then please either leave both websites out of this move - or create separate git repositories for each. Also does Apache offer an SVN Mirror for GIT? Regards, Dave On Feb 13, 2015, at 11:10 PM,

RE: [PROPOSAL] move repo to Git.

2015-02-14 Thread Dennis E. Hamilton
are read-only or my pairing is not working. I am not certain how to tell the difference. - Dennis -Original Message- From: Dennis E. Hamilton [mailto:dennis.hamil...@acm.org] Sent: Friday, February 13, 2015 10:41 To: dev@openoffice.apache.org Subject: RE: [PROPOSAL] move repo to Git

Re: [PROPOSAL] move repo to Git.

2015-02-14 Thread jan i
/incubator-corinthia.git) This is true for any GIT repo, and not only ASF. rgds jan I. - Dennis -Original Message- From: Dennis E. Hamilton [mailto:dennis.hamil...@acm.org] Sent: Friday, February 13, 2015 10:41 To: dev@openoffice.apache.org Subject: RE: [PROPOSAL] move repo to Git

RE: [PROPOSAL] move repo to Git.

2015-02-13 Thread Dennis E. Hamilton
Hamilton Subject: Re: [PROPOSAL] move repo to Git. On 13 February 2015 at 13:13, Dennis E. Hamilton dennis.hamil...@acm.org mailto:dennis.hamil...@acm.org wrote: Isn't having the mirror on GitHub an effective way to push changes to the SVN, especially for Apache committers who have project rights

Re: [PROPOSAL] move repo to Git.

2015-02-13 Thread jan i
[mailto:j...@apache.org javascript:;] Sent: Friday, February 13, 2015 04:41 To: dev; Dennis Hamilton Subject: Re: [PROPOSAL] move repo to Git. On 13 February 2015 at 13:13, Dennis E. Hamilton dennis.hamil...@acm.org javascript:; mailto:dennis.hamil...@acm.org javascript:; wrote: Isn't

Re: [PROPOSAL] move repo to Git.

2015-02-13 Thread Marcus
Am 02/13/2015 06:13 PM, schrieb Kay Schenk: On Fri, Feb 13, 2015 at 3:43 AM, jan ij...@apache.org wrote: Hi. We have now for a while had a readonly Git copy of our svn repo. Should we move to a full git repo, making it easier for new developers to participate (although it is in no way a

RE: [PROPOSAL] move repo to Git.

2015-02-13 Thread Dennis E. Hamilton
Message- From: jan i [mailto:j...@apache.org] Sent: Friday, February 13, 2015 09:04 To: dev@openoffice.apache.org; dennis.hamil...@acm.org Subject: Re: [PROPOSAL] move repo to Git. On Friday, February 13, 2015, Dennis E. Hamilton dennis.hamil...@acm.org wrote: I don’t understand the response

Re: [PROPOSAL] move repo to Git.

2015-02-13 Thread jan i
On 13 February 2015 at 18:13, Kay Schenk kay.sch...@gmail.com wrote: On Fri, Feb 13, 2015 at 3:43 AM, jan i j...@apache.org wrote: Hi. We have now for a while had a readonly Git copy of our svn repo. Should we move to a full git repo, making it easier for new developers to

Re: [PROPOSAL] move repo to Git.

2015-02-13 Thread Regina Henschel
Hi Jan, jan i schrieb: Hi. We have now for a while had a readonly Git copy of our svn repo. Should we move to a full git repo, making it easier for new developers to participate (although it is in no way a guarantee, that it will attract new people) by lowering the barrier. For more

Re: [PROPOSAL] move repo to Git.

2015-02-13 Thread Pedro Giffuni
Hello; I don't currently use git but what I use is not really important: if a move to git were to be considered, it would only make sense if we can rescue the pre-apache history and in particular the Hg CWSs. Just my $0.02, Pedro.

Re: [PROPOSAL] move repo to Git.

2015-02-13 Thread Kay Schenk
On Fri, Feb 13, 2015 at 3:43 AM, jan i j...@apache.org wrote: Hi. We have now for a while had a readonly Git copy of our svn repo. Should we move to a full git repo, making it easier for new developers to participate (although it is in no way a guarantee, that it will attract new people)

Re: [PROPOSAL] move repo to Git.

2015-02-13 Thread Alexandro Colorado
I think is a good idea to use Git as a full fledge repo. +1 On Fri, Feb 13, 2015 at 12:13 PM, Kay Schenk kay.sch...@gmail.com wrote: On Fri, Feb 13, 2015 at 3:43 AM, jan i j...@apache.org wrote: Hi. We have now for a while had a readonly Git copy of our svn repo. Should we move to a

RE: [PROPOSAL] move repo to Git.

2015-02-13 Thread Dennis E. Hamilton
Isn't having the mirror on GitHub an effective way to push changes to the SVN, especially for Apache committers who have project rights to the GitHub repo? Non-committer pull requests are as complicated either way, it seems to me, and the GitHub mirror might be superior for that. I assume the

Re: [PROPOSAL] move repo to Git.

2015-02-13 Thread jan i
On 13 February 2015 at 13:13, Dennis E. Hamilton dennis.hamil...@acm.org wrote: Isn't having the mirror on GitHub an effective way to push changes to the SVN, especially for Apache committers who have project rights to the GitHub repo? Non-committer pull requests are as complicated either