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/bJ6WYR6AgAAEtICAAY5HAIAAsYAAgACNfwCAAALqAA==
Date: Thu, 12 Nov 2015 17:59:57 +0000
Message-ID: <DBAC27A5-D685-4FD7-A837-AD928ECC4623@hortonworks.com>
References: 
 <CALwhT94_OW-Dg1F5wiBZBHTYgtyrEFLnzy+Yecyo6XL8BP8suQ@mail.gmail.com>
 <24B40D0D-1ADF-4AD7-910D-586D4F571BED@hortonworks.com>
 <EB84BE83-FAB6-4A95-82D4-3A87A6F4AF43@hortonworks.com>
 <CADbBEnsBDpZtxpRitQ=7UY04K3YNfh=uF91Z+d-dF8jK35VkLA@mail.gmail.com>
 <3D9E3DF7-9017-45F1-AFDB-C82A6073E6FD@hortonworks.com>
 <CADbBEnsNpn84Q5BX3V6RSzg54KxA9NOihu57H9Q+RRfRu3=Uow@mail.gmail.com>
In-Reply-To: 
 <CADbBEnsNpn84Q5BX3V6RSzg54KxA9NOihu57H9Q+RRfRu3=Uow@mail.gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
Content-Type: text/plain; charset="us-ascii"
Content-ID: <A5F0F32F1293864A9710A71CCB75C0A5@exch080.serverpod.net>
Content-Transfer-Encoding: quoted-printable


> On 12 Nov 2015, at 17:49, Sangjin Lee <sjlee0@gmail.com> wrote:
>=20
> Yes, I completely understand about the git branch naming practice (in fac=
t
> that's what I normally do). I was commenting on our hadoop patch naming
> convention. We are supposed to use patch names as
> "<jira-id>-<branch-name-if-not-trunk>.<sequence>.patch".
>=20
> If we used "feature/HADOOP-12345" as the git branch name and the subtask
> JIRA was HADOOP-67890 for example, the patch file name would be
> "HADOOP-67890-feature/HADOOP-12345.001.patch", which would not be doable,
> no? For that to work, we would need to have some kind of escaping
> convention which jenkins and users follow.
>=20

aah, now I follow. wouldn't HADOOP-12345.001.patch be enough?