Skip to content

Obtain release node name from Erlang VM instead of OS#553

Merged
tsloughter merged 1 commit intoerlware:masterfrom
lrascao:feature/fix_longname_releases
Dec 27, 2016
Merged

Obtain release node name from Erlang VM instead of OS#553
tsloughter merged 1 commit intoerlware:masterfrom
lrascao:feature/fix_longname_releases

Conversation

@lrascao
Copy link
Copy Markdown
Collaborator

@lrascao lrascao commented Dec 18, 2016

No description provided.

@lrascao lrascao mentioned this pull request Dec 18, 2016
@stuart-thackray
Copy link
Copy Markdown

Ty will try asap use rebar3 which brought me here will try test whereby figure out how to asap

@lrascao lrascao force-pushed the feature/fix_longname_releases branch from 0794874 to 261b5ae Compare December 18, 2016 21:15
@lrascao
Copy link
Copy Markdown
Collaborator Author

lrascao commented Dec 18, 2016

@stuart-thackray drop me a line if you're having trouble, i use this branch of rebar3 when i need to use a custom relx

@stuart-thackray
Copy link
Copy Markdown

The change looks good @lrascao 👍

@lrascao
Copy link
Copy Markdown
Collaborator Author

lrascao commented Dec 19, 2016

@tsloughter this is ready for review, we'll need to cut a new release for rebar3 to use after this

@tsloughter tsloughter merged commit 6ab0a49 into erlware:master Dec 27, 2016
@lrascao lrascao deleted the feature/fix_longname_releases branch December 27, 2016 18:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants