Skip to content
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.

Sign up for GitHub

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

Jump to bottom

'Update Project' should be more vocal when mcz file is dirty #84

Open
GoogleCodeExporter opened this issue Mar 24, 2015 · 2 comments
Open

'Update Project' should be more vocal when mcz file is dirty #84

GoogleCodeExporter opened this issue Mar 24, 2015 · 2 comments
Labels
auto-migrated Milestone-1.0 Priority-Medium Type-Defect

Comments

@GoogleCodeExporter
Copy link 

If you do an update project right now on a dirtied configuration, the update of 
the config is skipped and a message is printed to that effect in the 
Transcript, but if the target update is skipped, the 'Update Project' command 
should squawk a little louder and give you the option to load over the modified 
mcz file...

Original issue reported on code.google.com by henrichs...@gmail.com on 11 Jun 2010 at 5:10
@GoogleCodeExporter
Copy link
Author

Original comment by henrichs...@gmail.com on 18 Jan 2012 at 6:52

  • Added labels: Milestone-1.0-beta.32
  • Removed labels: ****

@GoogleCodeExporter
Copy link
Author

Original comment by henrichs...@gmail.com on 19 May 2012 at 7:59

  • Added labels: Milestone-1.0
  • Removed labels: Milestone-1.0-beta.32

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
auto-migrated Milestone-1.0 Priority-Medium Type-Defect
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@GoogleCodeExporter