Mailing-List: contact common-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-dev@hadoop.apache.org
Subject: Re: Need for force-push on feature branches
MIME-Version: 1.0
From: Steve Loughran <stevel@hortonworks.com>
To: "common-dev@hadoop.apache.org" <common-dev@hadoop.apache.org>
Thread-Topic: Need for force-push on feature branches
Thread-Index: AQHRHAQy5U71H+b3aUyIIRjxrME/bJ6WYR6A
Date: Tue, 10 Nov 2015 22:45:30 +0000
Message-ID: <24B40D0D-1ADF-4AD7-910D-586D4F571BED@hortonworks.com>
References: 
 <CALwhT94_OW-Dg1F5wiBZBHTYgtyrEFLnzy+Yecyo6XL8BP8suQ@mail.gmail.com>
In-Reply-To: 
 <CALwhT94_OW-Dg1F5wiBZBHTYgtyrEFLnzy+Yecyo6XL8BP8suQ@mail.gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
Content-Type: text/plain; charset="us-ascii"
Content-ID: <63BAE4A48475DB4F9FE0B11ECF9EA1C9@exch080.serverpod.net>
Content-Transfer-Encoding: quoted-printable


> On 10 Nov 2015, at 22:07, Karthik Kambatla <kasha@cloudera.com> wrote:
>=20
> Hi folks,
>=20
> Recently, Infra disabled force-pushes (and non-fast-forward pushes) to al=
l
> branches to avoid accidental overwrites or deletions.
>=20
> I propose we reach out to Infra and ask for an exemption since our workfl=
ow
> for feature branches involves deletions and force-pushes.
>=20

I asked them for this exemption for all branches called feature/* earlier t=
oday; its consistent with the git flow branch naming.=20

if all feature branches go in under there, people working on them are free =
to rebase as they choose.

> We should likely wait for a day or so to hear any concerns against this
> request. Also, can someone volunteer following up on this? I am going awa=
y
> on vacation shortly, and will have limited access to internet/email.
>=20