Re: To branch or to fork.

2017-09-25 Thread Daniel Gruno
gt;>> >>> Gj >>> >>> On Mon, Sep 25, 2017 at 12:54 AM, Geertjan Wielenga < >> geertjan.wiele...@googlemail.com> wrote: >>> >>>> The Apache Way is to branch, rather than fork -- the idea being >>>> that via >>>> branches,

Re: To branch or to fork.

2017-09-25 Thread Geertjan Wielenga
w+for+in > > frastructure-puppet+repo > > > > Gj > > > > On Mon, Sep 25, 2017 at 12:54 AM, Geertjan Wielenga < > geertjan.wiele...@googlemail.com> wrote: > > > > > The Apache Way is to branch, rather than fork -- the idea being > > >

Re: To branch or to fork.

2017-09-24 Thread Matthias Bläsing
le...@googlemail.com> wrote: > > > The Apache Way is to branch, rather than fork -- the idea being > > that via > > branches, the code stays at Apache, rather than being somewhere > > else, i.e., > > in someone else's Git repo. > > > > From the branch, reviews ar

Re: To branch or to fork.

2017-09-24 Thread Dave Schoorl
eertjan Wielenga < > geertjan.wiele...@googlemail.com> wrote: > > > > > > Hi all, > > > > The Apache Way is to branch, rather than fork -- the idea being > > that via > > branches, the code stays at A

Re: To branch or to fork.

2017-09-24 Thread Geertjan Wielenga
See: https://cwiki.apache.org/confluence/display/INFRA/Git+workflow+for+infrastructure-puppet+repo Gj On Mon, Sep 25, 2017 at 12:54 AM, Geertjan Wielenga < geertjan.wiele...@googlemail.com> wrote: > Hi all, > > The Apache Way is to branch, rather than fork -- the idea being that

To branch or to fork.

2017-09-24 Thread Geertjan Wielenga
Hi all, The Apache Way is to branch, rather than fork -- the idea being that via branches, the code stays at Apache, rather than being somewhere else, i.e., in someone else's Git repo. >From the branch, reviews are done, prior to merging. We'll (I'll) also stop pushing straight to the ASF r