rtems/rtems-docs
1
0
Fork 0
mirror of https://git.rtems.org/rtems-docs/ synced 2025-05-15 16:46:39 +08:00
Code Issues Packages Projects Releases Wiki Activity

eng: Unicode char (U+200B)

Browse Source
This commit is contained in:
Sebastian Huber 2018-12-20 08:19:05 +01:00
parent a7dc08331a
commit e24c5e9682
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
eng/vc-users.rst
View File

@ -53,7 +53,7 @@ the command:
This will create a local branch named "rtems410", containing the rtems-4.10 This will create a local branch named "rtems410", containing the rtems-4.10
release, that will track the remote branch "rtems-4-10-branch" in origin release, that will track the remote branch "rtems-4-10-branch" in origin
(​git://git.rtems.org/rtems.git). The ``git branch`` command prints a list of (git://git.rtems.org/rtems.git). The ``git branch`` command prints a list of
the current local branches, indicating the one currently checked out. the current local branches, indicating the one currently checked out.
If you want to switch between local branches: If you want to switch between local branches:
@ -284,7 +284,7 @@ git reset
``git reset`` is a powerful and tricky command that should only be used on ``git reset`` is a powerful and tricky command that should only be used on
local (un-pushed) branches): A good description of what it enables to do can be local (un-pushed) branches): A good description of what it enables to do can be
found ​here. The following are a few useful examples. Note that adding a ~ found here. The following are a few useful examples. Note that adding a ~
after HEAD refers to the most recent commit, and you can add a number after after HEAD refers to the most recent commit, and you can add a number after
the ~ to refer to commits even further back; HEAD by itself refers to the the ~ to refer to commits even further back; HEAD by itself refers to the
current working directory (changes since the last commit). current working directory (changes since the last commit).
@ -545,7 +545,7 @@ Troubleshooting
--------------- ---------------
Some restrictive corporate firewalls block access through the Git protocol Some restrictive corporate firewalls block access through the Git protocol
(​git://). If you are unable to reach the server ​git://git.rtems.org/ you can (git://). If you are unable to reach the server git://git.rtems.org/ you can
try accessing through http. To clone the rtems repository using the http try accessing through http. To clone the rtems repository using the http
protocol use the following command: protocol use the following command: