Skip to content

Update mbed trace #2887

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 3 commits into from
Oct 3, 2016
Merged

Update mbed trace #2887

merged 3 commits into from
Oct 3, 2016

Conversation

SeppoTakalo
Copy link
Contributor

Description

  • Fix a serious bug found from mbed-trace
  • Remove copy&pasted mbed-trace and replace it with git subtree add command. This allows us to track the history of remote repositories.

Status

READY

Migrations

NO

Related PRs

Seppo Takalo added 3 commits October 3, 2016 14:40
…t b17e969

git-subtree-dir: features/FEATURE_COMMON_PAL/mbed-trace
git-subtree-split: b17e96970777cdc61ba143bdd6ffc7b640aa6311
Next time, updating of mbed-trace is just:
```
git subtree pull --squash -m "Update mbed-trace" \
     -P features/FEATURE_COMMON_PAL/mbed-trace \
     [email protected]:ARMmbed/mbed-trace.git master
```
@SeppoTakalo
Copy link
Contributor Author

CC: @0xc0170 @sg- I recommend that this goes in before mbed OS 5.2 release. This is hard to replicate regression issue.

@sg- sg- added the needs: CI label Oct 3, 2016
@sg-
Copy link
Contributor

sg- commented Oct 3, 2016

/morph test

@mbed-bot
Copy link

mbed-bot commented Oct 3, 2016

Result: SUCCESS

Your command has finished executing! Here's what you wrote!

/morph test

Output

mbed Build Number: 1036

All builds and test passed!

@sg- sg- merged commit 5a55b39 into master Oct 3, 2016
@sg- sg- deleted the update_mbed_trace branch October 19, 2016 12:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants