Chromium Code Reviews Chromium Code Reviews
Issue 1385873002:
[Docs] Fix some nits discovered while converting to Markdown (Closed)
Base URL: https://chromium.googlesource.com/v8/v8.git@master| OLD | NEW |
|---|---|
| 1 **Quick links:** [browse](http://code.google.com/p/v8/source/browse) | [browse b leeding edge](http://code.google.com/p/v8/source/browse/branches/bleeding_edge) | [changes](https://chromium.googlesource.com/v8/v8.git). | 1 # Source |
| 2 | 2 |
| 3 **Quick links:** [browse](https://chromium.googlesource.com/v8/v8/) | [browse bl eeding edge](https://chromium.googlesource.com/v8/v8/+/master) | [changes](https ://chromium.googlesource.com/v8/v8/+log/master). | |
|
Michael Achenbach
2015/10/05 10:08:22
How about s/bleeding edge/master ? The phrase blee
Michael Hablich
2015/10/05 14:24:38
I will change it the next time I touch this file.
| |
| 4 | |
| 3 ## Command-Line Access | 5 ## Command-Line Access |
| 4 | 6 |
| 5 ### Git | 7 ### Git |
| 6 See [UsingGit](using_git.md). | 8 See [UsingGit](using_git.md). |
| 7 | 9 |
| 8 ### Subversion (deprecated) | 10 ### Subversion (deprecated) |
| 9 | 11 |
| 10 Use this command to anonymously check out the up-to-date stable version of the p roject source code: | 12 Use this command to anonymously check out the up-to-date stable version of the p roject source code: |
| 11 | 13 |
| 12 > `svn checkout http://v8.googlecode.com/svn/trunk/ v8` | 14 > `svn checkout http://v8.googlecode.com/svn/trunk/ v8` |
| (...skipping 16 matching lines...) Expand all Loading... | |
| 29 * Under `trunk/` is the "stable edge", which is updated a few times per week. It is a copy of the bleeding edge that has been successfully tested. Use this if you want to be almost up to date and don't want your code to break whenever we accidentally forget to add a file on the bleeding edge. Some of the trunk revisi ons are tagged with X.Y.Z.T version labels. When we decide which of X.Y.**.** is the "most stable", it becomes the X.Y branch in subversion. | 31 * Under `trunk/` is the "stable edge", which is updated a few times per week. It is a copy of the bleeding edge that has been successfully tested. Use this if you want to be almost up to date and don't want your code to break whenever we accidentally forget to add a file on the bleeding edge. Some of the trunk revisi ons are tagged with X.Y.Z.T version labels. When we decide which of X.Y.**.** is the "most stable", it becomes the X.Y branch in subversion. |
| 30 * If you want a well-tested version that doesn't change except for bugfixes, u se one of the versioned branches (e.g. `branches/3.16/` at the time of this writ ing). Note that usually only the last two branches are actively maintained; any older branches could have unfixed security holes. You may want to follow the V8 version that Chrome is shipping on its stable (or beta) channels, see http://oma haproxy.appspot.com. | 32 * If you want a well-tested version that doesn't change except for bugfixes, u se one of the versioned branches (e.g. `branches/3.16/` at the time of this writ ing). Note that usually only the last two branches are actively maintained; any older branches could have unfixed security holes. You may want to follow the V8 version that Chrome is shipping on its stable (or beta) channels, see http://oma haproxy.appspot.com. |
| 31 | 33 |
| 32 ## V8 public API compatibility | 34 ## V8 public API compatibility |
| 33 | 35 |
| 34 V8 public API (basically the files under include/ directory) may change over tim e. New types/methods may be added without breaking existing functionality. When we decide that want to drop some existing class/methods, we first mark it with [ V8\_DEPRECATED](https://code.google.com/p/chromium/codesearch#search/&q=V8_DEPRE CATED&sq=package:chromium&type=cs) macro which will cause compile time warnings when the deprecated methods are called by the embedder. We keep deprecated metho d for one branch and then remove it. E.g. if `v8::CpuProfiler::FindCpuProfile` w as plain non deprecated in _3.17_ branch, marked as `V8_DEPRECATED` in _3.18_, i t may well be removed in _3.19_ branch. | 36 V8 public API (basically the files under include/ directory) may change over tim e. New types/methods may be added without breaking existing functionality. When we decide that want to drop some existing class/methods, we first mark it with [ V8\_DEPRECATED](https://code.google.com/p/chromium/codesearch#search/&q=V8_DEPRE CATED&sq=package:chromium&type=cs) macro which will cause compile time warnings when the deprecated methods are called by the embedder. We keep deprecated metho d for one branch and then remove it. E.g. if `v8::CpuProfiler::FindCpuProfile` w as plain non deprecated in _3.17_ branch, marked as `V8_DEPRECATED` in _3.18_, i t may well be removed in _3.19_ branch. |
| 35 | 37 |
| 36 | 38 |
| 37 ## GUI and IDE Access | 39 ## GUI and IDE Access |
| 38 | 40 |
| 39 This project's Subversion repository may be accessed using many different client programs and plug-ins. See your client's documentation for more information. | 41 This project's Subversion repository may be accessed using many different client programs and plug-ins. See your client's documentation for more information. |
| OLD | NEW |
