[GitHub] davidzuhn commented on issue #157: Make it easier to pin a version to a specific tag

[GitBox <gi...@apache.org>]

davidzuhn commented on issue #157: Make it easier to pin a version to a specific tag
URL: https://github.com/apache/mynewt-newt/issues/157#issuecomment-380877871
 
 
   I see there being two issues here.   One is determining which source I wish to check out of github.   That can be identified by a commit, tag or branch.   The second is determining some semantic identification as to what's in that source, and that's where the project.yml file comes into play.   I could check something out from git that's entirely not a Newt project, or the wrong versions for dependencies, etc.   The checkout would succeed, but the semantic analysis would fail.    
   
   But these two items ought to be separated.   If project.yml always has to come from master, then changes to other branches or tags also need to be reflected in master, requiring additional work.  And that's work that's incompatible with at least one common workflow when dealing with private copies of upstream repositories.   
   
   I wouldn't mind at all keeping project.yml up to date (for my purposes), but only in the branches where I'm doing my own work.   Branches that are mirrored from elsewhere should remain unmodified.
   
   I'm not keen on having to keep updating my application with a new commit id every time I make a change in that upstream repo.   As things stand today, I don't change '0-dev' every time that master updates -- it follows the branch.   I'd really like to keep that capability.  I just want to be able to specify my own branches. 
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services