To install click the Add extension button. That's it.

The source code for the WIKI 2 extension is being checked by specialists of the Mozilla Foundation, Google, and Apple. You could also do it yourself at any point in time.

How to transfigure the Wikipedia

Would you like Wikipedia to always look as professional and up-to-date? We have created a browser extension. It will enhance any encyclopedic page you visit with the magic of the WIKI 2 technology.

Try it — you can delete it anytime.

Install in 5 seconds
4,5
Kelly Slayton
Congratulations on this excellent venture… what a great idea!
Alexander Grigorievskiy
I use WIKI 2 every day and almost forgot how the original Wikipedia looks like.
Live Statistics
English Articles
Improved in 24 Hours
Added in 24 Hours
What we do. Every page goes through several hundred of perfecting techniques; in live mode. Quite the same Wikipedia. Just better.
Great Wikipedia has got greater.
.
Leo
Newton
Brights
Milds

List of version-control software

From Wikipedia, the free encyclopedia

This is a list of notable software for version control.

YouTube Encyclopedic

  • 1/5
    Views:
    125 714
    385
    2 228
    59 738
    79 702
  • What Is Version Control? | Git Version Control | Version Control In Software Engineering|Simplilearn
  • Best Practices for HPC Software Developers: #3 "Distributed Version Control & CI Testing"
  • 3.3.11 Lab - Software Version Control with Git
  • Git Version Control _final_new_final.new - Computerphile
  • cPanel Tutorials - Git Version Control

Transcription

Local Data Model

In the local-only approach, all developers must use the same file system.

Open Source

  • Revision Control System (RCS) – stores the latest version and backward deltas for fastest access to the trunk tip[1][2] compared to SCCS and an improved user interface,[3] at the cost of slow branch tip access and missing support for included/excluded deltas.
  • Source Code Control System (SCCS) – part of UNIX; based on interleaved deltas, can construct versions as arbitrary sets of revisions. Extracting an arbitrary version takes essentially the same time and is thus more useful in environments that rely heavily on branching and merging with multiple "current" and identical versions.

Proprietary

Client–server model

In the client–server model, developers use one shared repository.

Open source

  • Concurrent Versions System (CVS) – originally built on RCS, licensed under the GPL.
    • CVSNT – cross-platform port of CVS that allows case insensitive file names among other changes
    • OpenCVS – unreleased CVS clone under a BSD license, emphasising security and source code correctness
  • Subversion (SVN) – versioning control system inspired by CVS[4]
  • Vesta – (discontinued) build system with a versioning file system and support for distributed repositories

Proprietary

Distributed model

In the distributed approach, each developer works directly with their own local repository, and changes are shared between repositories as a separate step.

Open source

  • BitKeeper – (discontinued) was used in Linux kernel development (2002 – April 2005) until its license was revoked for breach of contract; was open-sourced in 2016 in attempt to broaden its appeal again.
  • Darcs – written in Haskell, originally developed by David Roundy; can track inter-patch dependencies and automatically rearrange and cherry-pick them using a theory of patches
  • Fossil – written by D. Richard Hipp for SQLite; distributed revision control, wiki, bug-tracking, and forum (all-in-one solution) with console and web interfaces. Single portable executable and single repository file.
  • Git – written in a collection of Perl, C, and various shell scripts, designed by Linus Torvalds based on needs of the Linux kernel project; decentralized: goals: fast, flexible, and robust [5]
  • Mercurial – written in Python as an open source replacement to BitKeeper; decentralized and aims to be fast, lightweight, portable, and easy to use

Proprietary

Discontinued

These systems have been either officially discontinued or not shipped a release in more than a decade.

See also

References

  1. ^ Bill Wohler (10 Oct 1992). "Unix – Frequently Asked Questions (7/7)". RCS vs SCCS: How do they compare for performance?. [RCS ...] is much faster in retrieving the latest version
  2. ^ Larry McVoy (11 Dec 2003). "BitKeeper: Why SCCS, rather than RCS?". Archived from the original on March 26, 2012. RCS is optimized for getting the most recent version on the trunk
  3. ^ Bill Wohler (10 Oct 1992). "Unix – Frequently Asked Questions (7/7)". RCS vs SCCS: How do the interfaces compare?. [RCS ...] is more intuitive and consistent
  4. ^ "Changes", SVN, Collab Net, archived from the original on October 25, 2008
  5. ^ "Git - A Short History of Git". git-scm.com. Retrieved 2023-10-29.
  6. ^ "Plastic SCM - The Distributed Version Control for Big Projects". www.plasticscm.com. Retrieved 2023-10-29.
  7. ^ Technologies, Unity. "Scalable DevOps Services & Solutions | Unity". unity.com. Retrieved 2023-10-29.

External links

This page was last edited on 11 April 2024, at 14:00
Basis of this page is in Wikipedia. Text is available under the CC BY-SA 3.0 Unported License. Non-text media are available under their specified licenses. Wikipedia® is a registered trademark of the Wikimedia Foundation, Inc. WIKI 2 is an independent company and has no affiliation with Wikimedia Foundation.
Contact WIKI 2
Introduction
Terms of Service
Privacy Policy