hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Steve Loughran <ste...@hortonworks.com>
Subject Re: Need for force-push on feature branches
Date Thu, 12 Nov 2015 17:59:57 GMT

> On 12 Nov 2015, at 17:49, Sangjin Lee <sjlee0@gmail.com> wrote:
> 
> Yes, I completely understand about the git branch naming practice (in fact
> 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".
> 
> 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.
> 

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

Mime
View raw message