diff options
| author | Clay Murphy <claym@google.com> | 2014-09-11 10:32:47 -0700 |
|---|---|---|
| committer | Clay Murphy <claym@google.com> | 2014-10-28 16:35:55 -0700 |
| commit | b842dfce21a404126a26b693fcfaf17d3637f854 (patch) | |
| tree | bc1216cdba215655890ce3c8ba8b14d80207d05c | |
| parent | 460c688dba80441038975e41106eade3b2019a28 (diff) | |
| download | source.android.com-b842dfce21a404126a26b693fcfaf17d3637f854.tar.gz | |
Docs: Removing last external-link icon.
Bug: 17450294
Change-Id: I12f20f1f2fa0a779a79b39e832b0f3374bf9fcdc
Conflicts:
src/source/developing.jd
| -rw-r--r-- | src/source/developing.jd | 7 |
1 files changed, 3 insertions, 4 deletions
diff --git a/src/source/developing.jd b/src/source/developing.jd index 46a51a70..64c24c2c 100644 --- a/src/source/developing.jd +++ b/src/source/developing.jd @@ -72,10 +72,9 @@ For information about using repo to download source, see <a href="{@docRoot}sour <pre><code>$ repo sync PROJECT0 PROJECT1 PROJECT2 ... </code></pre> <h2 id="creating-topic-branches">Creating topic branches</h2> -<p>Start a topic branch in your local work environment whenever you begin a change, for example when you begin work on a bug or new feature. A topic branch is not a copy of the original files; it is a pointer to a particular commit. This makes creating local branches and switching among them a light-weight operation. By using branches, you can isolate one aspect of your work from the others. For an interesting article about using topic branches, see <a href="http://www.kernel.org/pub/software/scm/git/docs/howto/separating-topic-branches.txt">Separating topic branches</a>. -<img src="{@docRoot}images/external-link.png" alt=""></p> -<p>To start a topic branch using Repo: </p> -<pre><code>$ repo start BRANCH_NAME +<p>Start a topic branch in your local work environment whenever you begin a change, for example when you begin work on a bug or new feature. A topic branch is not a copy of the original files; it is a pointer to a particular commit. This makes creating local branches and switching among them a light-weight operation. By using branches, you can isolate one aspect of your work from the others. For an interesting article about using topic branches, see <a href="http://www.kernel.org/pub/software/scm/git/docs/howto/separating-topic-branches.txt">Separating topic branches</a>.</p> +<p>To start a topic branch using Repo, navigate into the project to be modified and issue: </p> +<pre><code>$ repo start BRANCH_NAME . </code></pre> <p>To verify that your new branch was created:</p> <pre><code>$ repo status |