Skip to content

Improve documentation (0.9.10) #379

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 1 commit into from
Oct 20, 2016
Merged

Conversation

screamerbg
Copy link
Contributor

@screamerbg screamerbg commented Oct 19, 2016

Reviewers:

@@ -691,6 +691,22 @@ As with any mbed CLI command, `mbed update` uses the current directory as a work

<span class="tips">**Tip: Synchronizing library references:** Before triggering an update, you might want to synchronize any changes that you've made to the program structure by running ``mbed sync``, which will update the necessary library references and get rid of the invalid ones.</span>

## Publishing local program or library
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Publishing a local program or library

@@ -691,6 +691,22 @@ As with any mbed CLI command, `mbed update` uses the current directory as a work

<span class="tips">**Tip: Synchronizing library references:** Before triggering an update, you might want to synchronize any changes that you've made to the program structure by running ``mbed sync``, which will update the necessary library references and get rid of the invalid ones.</span>

## Publishing local program or library

When you create new (local) source control managed program or library, all revision history will exist only locally and the repository wouldn't be associated with remote one. To publish the local repository (while preserving the revision history) please follow these steps:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

When you create a new (local) source-control managed program or library, its revision history exists only locally; the repository is not associated with the remote one. To publish the local repository without losing its revision history, please follow these steps:

## Publishing local program or library

When you create new (local) source control managed program or library, all revision history will exist only locally and the repository wouldn't be associated with remote one. To publish the local repository (while preserving the revision history) please follow these steps:
1. Create new empty repository on the remote side - either based on public repository hosting service (Github, Bitbucket, mbed.org), service of your own or even different location on your system
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  1. Create a new empty repository on the remote site. This can be based on a public repository hosting service (GitHub, Bitbucket, mbed.org), your own service or even a different location on your system.


When you create new (local) source control managed program or library, all revision history will exist only locally and the repository wouldn't be associated with remote one. To publish the local repository (while preserving the revision history) please follow these steps:
1. Create new empty repository on the remote side - either based on public repository hosting service (Github, Bitbucket, mbed.org), service of your own or even different location on your system
2. Copy the URL/location of the new repository in your clipboard and open command line in the local repository directory (for example change directory to `mbed-os-example/local-lib`).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  1. Copy the URL of the new repository to your clipboard.
  2. Open a command line in the local repository directory (for example, change directory to mbed-os-example/local-lib).

3. To associate the local repository:
* For Git - run `git remote add origin <url-or-paht-to-your-remote-repo>`
* For Mercurial - edit .hg/hgrc and add (or replace if exists):
```
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Add a line break before the code, then indent the code by four spaces. This will place it as a code block in the numbered list, and continue the numbering after the code block.

[paths]
default = <url-or-paht-to-your-remote-repo>
```
4. Run `mbed publish` to publish your changes
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please add a period to the end of steps. It's not a universal law but it's the ARM style

```
4. Run `mbed publish` to publish your changes

In scanario with nested local repositories, start with the leaf repositories first.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"In a scenario"
"start with the leaf repositories" (you don't need "first" - you already said "start with")

@@ -54,11 +54,11 @@ mbed CLI is supported on Windows, Linux and Mac OS X. We're keen to learn about

### Requirements

* **Python** - mbed CLI is a Python script, so you'll need Python in order to use it. mbed CLI was tested with [version 2.7.9 of Python](https://www.python.org/download/releases/2.7/).
* **Python** - mbed CLI is a Python script, so you'll need Python in order to use it. mbed CLI was tested with [version 2.7.9 of Python](https://www.python.org/download/releases/2.7/) and is not compatible with Python 3 at the moment of this writing.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You don't need "of this writing"

* [Git](https://git-scm.com/).
* [Mercurial](https://www.mercurial-scm.org/).
* [Git](https://git-scm.com/) - version 1.9.5 or later
* [Mercurial](https://www.mercurial-scm.org/) - version or 2.2.2 or later
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"version 2.2.2 or later" (I assume that other "or" is there by mistake)

@screamerbg screamerbg force-pushed the development branch 2 times, most recently from 6dac1b8 to 0d74efd Compare October 19, 2016 15:07
@@ -54,11 +54,11 @@ mbed CLI is supported on Windows, Linux and Mac OS X. We're keen to learn about

### Requirements

* **Python** - mbed CLI is a Python script, so you'll need Python in order to use it. mbed CLI was tested with version 2.7.9 of Python. You can download that or a newer version [here](https://www.python.org/downloads/).
* **Python** - mbed CLI is a Python script, so you'll need Python in order to use it. mbed CLI was tested with [version 2.7.9 of Python](https://www.python.org/download/releases/2.7/) and is not compatible with Python 3 at the moment of this writing.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think other tools (htrun need python 2.7.11)

Add documentation for publishing local/new repositories ARMmbed#362
Add documentation regarding the specific Python, Git and Mercurial versions that mbed CLI supports ARMmbed#376
@sg-
Copy link
Contributor

sg- commented Oct 20, 2016

LGTM 👍

@screamerbg screamerbg merged commit fbbc9dd into ARMmbed:master Oct 20, 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.

3 participants