You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@incubator.apache.org by "Noel J. Bergman" <no...@devtech.com> on 2010/10/01 01:13:14 UTC
RE: Podling to use native git
> Does any other podling use git-only workflow.
No ASF project is permitted to use git-only. And the typical git workflow is part of the problem. We strongly believe in a single, central, repository as part of the process of community building. The git model is better suited to disparate groups partially sharing a codebase.
Fundamentally, we WANT people working in a central, shared, repository.
If/when the ASF allows git as a technology, you can expect that the workflow will be an ASF workflow. And once Greg gets offline commmit working with SVN, I suspect that it will be harder to push for git.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: Podling to use native git
Posted by Guillaume Nodet <gn...@gmail.com>.
On Fri, Oct 1, 2010 at 09:44, Gav... <ga...@16degrees.com.au> wrote:
>
>
> > -----Original Message-----
> > From: Guillaume Nodet [mailto:gnodet@gmail.com]
> > Sent: Friday, 1 October 2010 5:11 PM
> > To: general@incubator.apache.org
> > Subject: Re: Podling to use native git
> >
> > I do agree with you. I don't really get this argument either.
> >
> > But in the meantime, you need to use an svn backend, and ask for a git
> > mirror. You can then fork / merge at github the way you want, merge
> > back
> > into trunk and git svn dcommit from there.
> >
> > I think it's really worse, as branches aren't maintained anymore in the
> > apache svn area,
>
> What's wrong with 'git tag' ??
>
What I'm saying is that having to maintain some branches at github outside
of svn in git is not the best thing. But that's really the only option we
have here.
>
>
> > but that's what we need to live with until git can be
> > properly supported at Apache.
>
> It will be a while.
>
>
> Gav...
>
> >
> > On Fri, Oct 1, 2010 at 08:49, Mark Struberg <st...@yahoo.de> wrote:
> >
> > > Hmm, to be honest, I don't see this argument. Because you can also
> > use a
> > > centralised model with GIT.
> > >
> > > Also, the main benefit of GIT is not only that you can do offline
> > commits,
> > > but mostly that it's sooo much easier to merge!
> > > I had a merge hell with my colleague in the company this week. He
> > kept a
> > > SVN feature branch for only one week and merging his feature branch
> > into the
> > > trunk (team with 10 developers) did cost us a whole day...
> > >
> > > The reason is that SVN applies an end to end diff while git aims to
> > merge
> > > by walking the commit tree of the branch and applying each commit
> > > separately.
> > >
> > > GIT even supports signing off commits. So each committer who pushes
> > to the
> > > central repo 'signs' that the contribution is ASL licensed.
> > >
> > > LieGrue,
> > > stru
> > >
> > > --- On Thu, 9/30/10, Noel J. Bergman <no...@devtech.com> wrote:
> > >
> > > > From: Noel J. Bergman <no...@devtech.com>
> > > > Subject: RE: Podling to use native git
> > > > To: general@incubator.apache.org
> > > > Date: Thursday, September 30, 2010, 11:13 PM
> > > > > Does any other podling use
> > > > git-only workflow.
> > > >
> > > > No ASF project is permitted to use git-only. And the
> > > > typical git workflow is part of the problem. We
> > > > strongly believe in a single, central, repository as part of
> > > > the process of community building. The git model is
> > > > better suited to disparate groups partially sharing a
> > > > codebase.
> > > >
> > > > Fundamentally, we WANT people working in a central, shared,
> > > > repository.
> > > >
> > > > If/when the ASF allows git as a technology, you can expect
> > > > that the workflow will be an ASF workflow. And once
> > > > Greg gets offline commmit working with SVN, I suspect that
> > > > it will be harder to push for git.
> > > >
> > > > --- Noel
> > > >
> > > >
> > > >
> > > > -------------------------------------------------------------------
> > --
> > > > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > > > For additional commands, e-mail: general-help@incubator.apache.org
> > > >
> > > >
> > >
> > >
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > > For additional commands, e-mail: general-help@incubator.apache.org
> > >
> > >
> >
> >
> > --
> > Cheers,
> > Guillaume Nodet
> > ------------------------
> > Blog: http://gnodet.blogspot.com/
> > ------------------------
> > Open Source SOA
> > http://fusesource.com
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com
RE: Podling to use native git
Posted by "Gav..." <ga...@16degrees.com.au>.
> -----Original Message-----
> From: Guillaume Nodet [mailto:gnodet@gmail.com]
> Sent: Friday, 1 October 2010 5:11 PM
> To: general@incubator.apache.org
> Subject: Re: Podling to use native git
>
> I do agree with you. I don't really get this argument either.
>
> But in the meantime, you need to use an svn backend, and ask for a git
> mirror. You can then fork / merge at github the way you want, merge
> back
> into trunk and git svn dcommit from there.
>
> I think it's really worse, as branches aren't maintained anymore in the
> apache svn area,
What's wrong with 'git tag' ??
> but that's what we need to live with until git can be
> properly supported at Apache.
It will be a while.
Gav...
>
> On Fri, Oct 1, 2010 at 08:49, Mark Struberg <st...@yahoo.de> wrote:
>
> > Hmm, to be honest, I don't see this argument. Because you can also
> use a
> > centralised model with GIT.
> >
> > Also, the main benefit of GIT is not only that you can do offline
> commits,
> > but mostly that it's sooo much easier to merge!
> > I had a merge hell with my colleague in the company this week. He
> kept a
> > SVN feature branch for only one week and merging his feature branch
> into the
> > trunk (team with 10 developers) did cost us a whole day...
> >
> > The reason is that SVN applies an end to end diff while git aims to
> merge
> > by walking the commit tree of the branch and applying each commit
> > separately.
> >
> > GIT even supports signing off commits. So each committer who pushes
> to the
> > central repo 'signs' that the contribution is ASL licensed.
> >
> > LieGrue,
> > stru
> >
> > --- On Thu, 9/30/10, Noel J. Bergman <no...@devtech.com> wrote:
> >
> > > From: Noel J. Bergman <no...@devtech.com>
> > > Subject: RE: Podling to use native git
> > > To: general@incubator.apache.org
> > > Date: Thursday, September 30, 2010, 11:13 PM
> > > > Does any other podling use
> > > git-only workflow.
> > >
> > > No ASF project is permitted to use git-only. And the
> > > typical git workflow is part of the problem. We
> > > strongly believe in a single, central, repository as part of
> > > the process of community building. The git model is
> > > better suited to disparate groups partially sharing a
> > > codebase.
> > >
> > > Fundamentally, we WANT people working in a central, shared,
> > > repository.
> > >
> > > If/when the ASF allows git as a technology, you can expect
> > > that the workflow will be an ASF workflow. And once
> > > Greg gets offline commmit working with SVN, I suspect that
> > > it will be harder to push for git.
> > >
> > > --- Noel
> > >
> > >
> > >
> > > -------------------------------------------------------------------
> --
> > > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > > For additional commands, e-mail: general-help@incubator.apache.org
> > >
> > >
> >
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > For additional commands, e-mail: general-help@incubator.apache.org
> >
> >
>
>
> --
> Cheers,
> Guillaume Nodet
> ------------------------
> Blog: http://gnodet.blogspot.com/
> ------------------------
> Open Source SOA
> http://fusesource.com
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: Podling to use native git
Posted by Guillaume Nodet <gn...@gmail.com>.
I do agree with you. I don't really get this argument either.
But in the meantime, you need to use an svn backend, and ask for a git
mirror. You can then fork / merge at github the way you want, merge back
into trunk and git svn dcommit from there.
I think it's really worse, as branches aren't maintained anymore in the
apache svn area, but that's what we need to live with until git can be
properly supported at Apache.
On Fri, Oct 1, 2010 at 08:49, Mark Struberg <st...@yahoo.de> wrote:
> Hmm, to be honest, I don't see this argument. Because you can also use a
> centralised model with GIT.
>
> Also, the main benefit of GIT is not only that you can do offline commits,
> but mostly that it's sooo much easier to merge!
> I had a merge hell with my colleague in the company this week. He kept a
> SVN feature branch for only one week and merging his feature branch into the
> trunk (team with 10 developers) did cost us a whole day...
>
> The reason is that SVN applies an end to end diff while git aims to merge
> by walking the commit tree of the branch and applying each commit
> separately.
>
> GIT even supports signing off commits. So each committer who pushes to the
> central repo 'signs' that the contribution is ASL licensed.
>
> LieGrue,
> stru
>
> --- On Thu, 9/30/10, Noel J. Bergman <no...@devtech.com> wrote:
>
> > From: Noel J. Bergman <no...@devtech.com>
> > Subject: RE: Podling to use native git
> > To: general@incubator.apache.org
> > Date: Thursday, September 30, 2010, 11:13 PM
> > > Does any other podling use
> > git-only workflow.
> >
> > No ASF project is permitted to use git-only. And the
> > typical git workflow is part of the problem. We
> > strongly believe in a single, central, repository as part of
> > the process of community building. The git model is
> > better suited to disparate groups partially sharing a
> > codebase.
> >
> > Fundamentally, we WANT people working in a central, shared,
> > repository.
> >
> > If/when the ASF allows git as a technology, you can expect
> > that the workflow will be an ASF workflow. And once
> > Greg gets offline commmit working with SVN, I suspect that
> > it will be harder to push for git.
> >
> > --- Noel
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > For additional commands, e-mail: general-help@incubator.apache.org
> >
> >
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com
RE: Podling to use native git
Posted by Mark Struberg <st...@yahoo.de>.
Hmm, to be honest, I don't see this argument. Because you can also use a centralised model with GIT.
Also, the main benefit of GIT is not only that you can do offline commits, but mostly that it's sooo much easier to merge!
I had a merge hell with my colleague in the company this week. He kept a SVN feature branch for only one week and merging his feature branch into the trunk (team with 10 developers) did cost us a whole day...
The reason is that SVN applies an end to end diff while git aims to merge by walking the commit tree of the branch and applying each commit separately.
GIT even supports signing off commits. So each committer who pushes to the central repo 'signs' that the contribution is ASL licensed.
LieGrue,
stru
--- On Thu, 9/30/10, Noel J. Bergman <no...@devtech.com> wrote:
> From: Noel J. Bergman <no...@devtech.com>
> Subject: RE: Podling to use native git
> To: general@incubator.apache.org
> Date: Thursday, September 30, 2010, 11:13 PM
> > Does any other podling use
> git-only workflow.
>
> No ASF project is permitted to use git-only. And the
> typical git workflow is part of the problem. We
> strongly believe in a single, central, repository as part of
> the process of community building. The git model is
> better suited to disparate groups partially sharing a
> codebase.
>
> Fundamentally, we WANT people working in a central, shared,
> repository.
>
> If/when the ASF allows git as a technology, you can expect
> that the workflow will be an ASF workflow. And once
> Greg gets offline commmit working with SVN, I suspect that
> it will be harder to push for git.
>
> --- Noel
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org