Skip to content

A trunk full of fixes and improvements #2 #51

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 27 commits into from
Apr 11, 2016
Merged

A trunk full of fixes and improvements #2 #51

merged 27 commits into from
Apr 11, 2016

Conversation

screamerbg
Copy link
Contributor

Introduces

  • Local repository support
  • neo.py new <git|hg> <name|path> - creates local program or library
  • neo.py update --ignore - allows receiving of updates even if local repositories are present (they are also preserved)
  • neo.py update --force - clears up all local uncommitted changes and also local repositories if they don't belong in the revision the codebase that is being updated to
  • Significant help improvements
  • Various fixes to behavior and consistency of update

…n "origin" (but prefers "origin" if present)
…committed changes or unpublished revisions. Currently used as safe mechanism for update() where a sub-repository has been removed or remote URL has been changed between revisions

Also sync before updating so the update process scans all .lib files
… handles due to rmtree_readonly() inside with open()..
…they don't exist in the requested revision (reproducibility)
… during publish and encourage the user to associate with remote repo
…y based on the specified source control management system
…ry command.

Polish help messages based on the current working context.
Make use of the findroot() to execute compile, export, toolchain and target commands in the program even if current working dir is inside a library
…pdate from remote repositories regardless of local repositories, uncommitted changes or unpublished revisions (and try to preserve them all)
@bogdanm
Copy link
Contributor

bogdanm commented Apr 11, 2016

I'm not going to pretend that I understand all the changes in here, but I assume you've tested them, so +1 from me.
Does the README need to be updated?

@screamerbg
Copy link
Contributor Author

Sorry README has not been updated. I will do that in a minute. Don't accept it yet

@bogdanm
Copy link
Contributor

bogdanm commented Apr 11, 2016

I +1'd it already, so feel free to merge it whenever you want. I assumed that the README wasn't updated yet due to time constraints.

@screamerbg screamerbg merged commit 3972383 into ARMmbed:master Apr 11, 2016
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.

2 participants