Rob
>>>>> has, that there may be many more downstream users that are on Git and that
>>>>> our being on Git would facilitate accepting appropriately-offered pull
>>>>> requests to the AOO repository. It seems this is a lower-frictio
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
s
>>>
>>> -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
nding 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 to ge
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.
[ ... ]
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
---
2015 02:54
To: dev@openoffice.apache.org
Subject: Re: [PROPOSAL] move repo to Git.
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,
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
--
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
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 p
-- 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
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/
http://svn.apach
On Fri, Feb 13, 2015 at 9:53 AM, jan i wrote:
> On 13 February 2015 at 18:13, Kay Schenk wrote:
>
> > On Fri, Feb 13, 2015 at 3:43 AM, jan i 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
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 las
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 wha
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 Ap
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.
-
-- 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
wrote:
> Corinthia has its code tree (not web site) on Git. There i
://git.apache.org/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.o
ors 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
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, Mec
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, MacOSX,
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 wrote:
> On Fri, Feb 13, 2015 at 3:43 AM, jan i 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 i
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 documenta
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.
---
ginal 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
wrote:
> I don’t understand the response. I said GitHu
Am 02/13/2015 06:13 PM, schrieb Kay Schenk:
On Fri, Feb 13, 2015 at 3:43 AM, jan i 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
On 13 February 2015 at 18:13, Kay Schenk wrote:
> On Fri, Feb 13, 2015 at 3:43 AM, jan i 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
On Fri, Feb 13, 2015 at 3:43 AM, jan i 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) by lowerin
idea what you mean.
rgds
jan I
>
> - Dennis
>
> From: jan i [mailto:j...@apache.org ]
> 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 &l
Hamilton
Subject: Re: [PROPOSAL] move repo to Git.
On 13 February 2015 at 13:13, Dennis E. Hamilton 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 to the
-Original Message-
> From: jan i [mailto:j...@apache.org]
> Sent: Friday, February 13, 2015 03:44
> To: dev
> Subject: [PROPOSAL] move repo to Git.
>
> 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
ution of
features.
-Original Message-
From: jan i [mailto:j...@apache.org]
Sent: Friday, February 13, 2015 03:44
To: dev
Subject: [PROPOSAL] move repo to Git.
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 fo
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 documentation on Git at Apache see
34 matches
Mail list logo
