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,
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
> > >
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
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
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
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