F5/unison
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

fixing dead links

Browse Source
This commit is contained in:
Gabriel Ferreira
2022-06-06 01:24:09 -03:00
parent a1580a5bd0
commit 60e1e4032c
139 changed files with 244 additions and 245 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
doc/manual/source/working-with-git.rst
View File

@@ -64,7 +64,7 @@ Assume that you are the user *john* on GitLab.com and that you want to create a
Note that you may only do this once; if you try to fork again, Gitlab will take you to the page of the original fork. So, if you are planning to maintain two or more separate forks (for example, one for your private work, another for maintenance, etc.), you are doing a mistake. Instead, you should add these forks as a remote of your existing directory (see below for adding remotes). Usually, it is a good thing to add the maintainer's repository as remotes, because it can happen that "bleeding edge" features will appear there before landing in ns-3-dev.
For more information on forking with Gilab, there is plenty of visual documentation (https://docs.gitlab.com/ee/gitlab-basics/fork-project.html). To work with your forked repository, you have two ways: one is a clean clone while the other is meant to re-use an existing ns-3 git repository.
For more information on forking with Gilab, there is plenty of visual documentation (https://docs.gitlab.com/ee/user/project/repository/forking_workflow.html). To work with your forked repository, you have two ways: one is a clean clone while the other is meant to re-use an existing ns-3 git repository.
Clone your forked repository on your machine
============================================