-1

As a lot of work will have to be done in a collaborative fashion. This should 
be allowed to happen in the repo and not outside.

So in not against external prs, I'm against forbidding internal ones.

Chris

Outlook für Android<https://aka.ms/ghei36> herunterladen

________________________________
From: Kenneth Knowles <[email protected]>
Sent: Wednesday, May 15, 2019 7:54:01 PM
To: [email protected]
Subject: Re: Git branches

+1 to fork & PR. It works great.

*From: *Lars Francke <[email protected]>
*Date: *Wed, May 15, 2019 at 9:58 AM
*To: * <[email protected]>

Hi,
>
> I'm not sure how other projects do this (well, I do, but not all of them)
> but I'd be in favor of keeping the Git branches we have clean (i.e. not
> having feature branches in the Apache repository).
>
> They tend to be forgotten, they are often not documented and can be
> confusing. I'd be in favor of developing in your own fork and then
> submitting a PR.
>
> What do others think?
>
> Cheers,
> Lars
>

Reply via email to