You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@mynewt.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2017/05/18 23:01:04 UTC

[jira] [Commented] (MYNEWT-583) Allow project.yml to specify a commit hash

    [ https://issues.apache.org/jira/browse/MYNEWT-583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16016613#comment-16016613 ] 

ASF subversion and git services commented on MYNEWT-583:
--------------------------------------------------------

Commit 26b618f3df44c01a721ec59df3120f1ed758e06e in incubator-mynewt-newt's branch refs/heads/master from [~marko]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-mynewt-newt.git;h=26b618f ]

MYNEWT-583; newt - allow use of specific tag/repository revision.


> Allow project.yml to specify a commit hash
> ------------------------------------------
>
>                 Key: MYNEWT-583
>                 URL: https://issues.apache.org/jira/browse/MYNEWT-583
>             Project: Mynewt
>          Issue Type: Bug
>          Components: Newt
>    Affects Versions: v1_0_0_rel
>            Reporter: Simon Ratner
>            Assignee: Marko Kiiskila
>             Fix For: v1_1_0_rel
>
>
> Would be great if one could lock down a specific mynewt-core commit hash in project.yml, in addition to tags. Currently, one tags are supported, but when using develop/latest it is more useful to test against a fixed known state.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)