Коммит cce2616e создал по автору Marcel Amirault's avatar Marcel Amirault Зафиксировано автором Achilleas Pipinellis
Просмотр файлов

Rename tfs.md to tfvc.md and update 

the tfs.md doc was actually about tfvc, so it was renamed
and content made more up to date, with light copy edits
владелец c77797ea
Скрыть пробелы
Построчно Рядом
doc/user/project/import/index.md
Просмотр файла @ cce2616e
......@@ -10,7 +10,7 @@
1. [From Gitea](gitea.md)
1. [From Perforce](perforce.md)
1. [From SVN](svn.md)
1. [From TFS](tfs.md)
1. [From TFVC](tfvc.md)
1. [From repo by URL](repo_by_url.md)
1. [By uploading a manifest file (AOSP)](manifest.md)
1. [From Gemnasium](gemnasium.md)
......
doc/user/project/import/tfs.md
Просмотр файла @ cce2616e
# Migrating from TFS
---
redirect_to: 'tfvc.md'
---
[TFS](https://azure.microsoft.com/en-us/services/devops/server/) is a set of tools developed by Microsoft
which also includes a centralized version control system (TFVC) similar to Git.
In this document, we emphasize on the TFVC to Git migration.
## TFVC vs Git
The following list illustrates the main differences between TFVC and Git:
- **Git is distributed** whereas TFVC is centralized using a client-server
architecture. This translates to Git having a more flexible workflow since
your working area is a copy of the entire repository. This decreases the
overhead when switching branches or merging for example, since you don't have
to communicate with a remote server.
- **Storage method.** Changes in CVS are per file (changeset), while in Git
a committed file(s) is stored in its entirety (snapshot). That means that's
very easy in Git to revert or undo a whole change.
Check also Microsoft's documentation on the
[comparison of Git and TFVC](https://docs.microsoft.com/en-us/azure/devops/repos/tfvc/comparison-git-tfvc?view=azure-devops)
and the Wikipedia
[comparison of version control software](https://en.wikipedia.org/wiki/Comparison_of_version_control_software).
## Why migrate
Migrating to Git/GitLab there is:
- **No licensing costs**, Git is GPL while TFVC is proprietary.
- **Shorter learning curve**, Git has a big community and a vast number of
tutorials to get you started (see our [Git topic](../../../topics/git/index.md)).
- **Integration with modern tools**, migrating to Git and GitLab you can have
an open source end-to-end software development platform with built-in version
control, issue tracking, code review, CI/CD, and more.
## How to migrate
The best option to migrate from TFVC to Git is to use the
[`git-tfs`](https://github.com/git-tfs/git-tfs) tool. A specific guide for the
migration exists:
[Migrate TFS to Git](https://github.com/git-tfs/git-tfs/blob/master/doc/usecases/migrate_tfs_to_git.md).
This document was moved to [another location](tfvc.md).
doc/user/project/import/tfvc.md 0 → 100644
Просмотр файла @ cce2616e
---
type: concepts
---
# Migrating from TFVC to Git
Team Foundation Server (TFS), renamed [Azure DevOps Server](https://azure.microsoft.com/en-us/services/devops/server/)
in 2019, is a set of tools developed by Microsoft which also includes
[Team Foundation Version Control](https://docs.microsoft.com/en-us/azure/devops/repos/tfvc/overview)
(TFVC), a centralized version control system similar to Git.
In this document, we focus on the TFVC to Git migration.
## TFVC vs Git
The main differences between TFVC and Git are:
- **Git is distributed:** While TFVC is centralized using a client-server architecture,
Git is distributed. This translates to Git having a more flexible workflow since
you work with a copy of the entire repository. This allows you to quickly
switch branches or merge, for example, without needing to communicate with a remote server.
- **Storage:** Changes in a centralized version control system are per file (changeset),
while in Git a committed file is stored in its entirety (snapshot). That means that it is
very easy to revert or undo a whole change in Git.
For more information, see:
- Microsoft's [comparison of Git and TFVC](https://docs.microsoft.com/en-us/azure/devops/repos/tfvc/comparison-git-tfvc?view=azure-devops).
- The Wikipedia [comparison of version control software](https://en.wikipedia.org/wiki/Comparison_of_version_control_software).
## Why migrate
Advantages of migrating to Git/GitLab:
- **No licensing costs:** Git is open source, while TFVC is proprietary.
- **Shorter learning curve:** Git has a big community and a vast number of
tutorials to get you started (see our [Git topic](../../../topics/git/index.md)).
- **Integration with modern tools:** After migrating to Git and GitLab, you will have
an open source, end-to-end software development platform with built-in version
control, issue tracking, code review, CI/CD, and more.
## How to migrate
The best option to migrate from TFVC to Git is to use the [`git-tfs`](https://github.com/git-tfs/git-tfs)
tool. Read the [Migrate TFS to Git](https://github.com/git-tfs/git-tfs/blob/master/doc/usecases/migrate_tfs_to_git.md)
guide for more details.
Поддерживает Markdown
0% или .
You are about to add 0 people to the discussion. Proceed with caution.
Сначала завершите редактирование этого сообщения!
Пожалуйста, зарегистрируйтесь или чтобы прокомментировать