DOCSLIB.ORG

Collabnet Subversion Edge User Guide 2 | Subversion Edge | TOC

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Collabnet Subversion Edge User Guide 2 | Subversion Edge | TOC CollabNet Subversion Edge User Guide 2 | Subversion Edge | TOC Contents Welcome to CollabNet Subversion Edge.............................................................................7 Set up Subversion Edge .......................................................................................................8 Install Subversion Edge ...........................................................................................................................8 Install Subversion Edge on Windows...........................................................................................8 Install Subversion Edge on Linux................................................................................................9 Install Subversion Edge on Solaris.............................................................................................10 Configure the server...............................................................................................................................12 Configure general server settings...............................................................................................12 Configure advanced server settings............................................................................................13 Configure authentication settings...............................................................................................13 Configure a proxy server............................................................................................................14 Configure the mail server...........................................................................................................14 Configure log settings................................................................................................................15 Configure server monitoring......................................................................................................15 Upgrade Subversion Edge .................................................................................................16 Update Subversion Edge from the console............................................................................................16 Upgrade Subversion Edge manually......................................................................................................16 Manage repositories............................................................................................................17 Create a repository.................................................................................................................................17 Connect an existing repository...............................................................................................................17 Define repository access rules................................................................................................................18 Schedule repository backups..................................................................................................................19 Dump a repository..................................................................................................................................20 Load a repository....................................................................................................................................22 Verify repository data.............................................................................................................................23 Create a repository template...................................................................................................................23 Manage hook scripts...............................................................................................................................24 Monitor the disk space used by a repository..........................................................................................24 Delete a repository.................................................................................................................................24 Manage users ......................................................................................................................26 Create a Subversion Edge user account.................................................................................................26 Edit a user account.................................................................................................................................27 Edit a role...............................................................................................................................................27 Set up Subversion Edge as a TeamForge server...............................................................28 Convert to a TeamForge SCM integration server...................................................................................28 Get the TeamForge Integration API Key................................................................................................30 Import TeamForge's self-signed SSL certificate....................................................................................30 Convert to standalone mode...................................................................................................................31 Replication...........................................................................................................................32 Overview................................................................................................................................................32 Subversion Edge | TOC | 3 Convert to a replica server in TeamForge...............................................................................................33 Monitoring a replica server....................................................................................................................39 Update TeamForge account for replica mode.........................................................................................40 Update replica retry settings...................................................................................................................41 Convert to standalone mode...................................................................................................................41 Status icons for replica jobs...................................................................................................................42 Extend Subversion Edge with the CollabNet cloud.........................................................43 What is a cloud backup?.........................................................................................................................43 Schedule a cloud backup........................................................................................................................43 Access a cloud backup...........................................................................................................................44 Restore a repository from a cloud backup..............................................................................................44 Maintain your Subversion Edge site.................................................................................46 Monitor server health.............................................................................................................................46 Monitor server logs................................................................................................................................46 Monitor jobs...........................................................................................................................................47 Subversion Edge FAQ.........................................................................................................48 Can I use the web console with my custom Apache configuration? .....................................................48 When I try to browse repositories I am getting an Internal Server Error. How do I fix this? ...............48 How do I migrate from my existing Subversion installation to Subversion Edge?................................48 Using Subversion with TeamForge........................................................................................................48 Can I use a Subversion 1.7.x client with my TeamForge 6.1.1 server? .....................................48 Can I upgrade the Subversion server installed by TeamForge to version 1.7.x? .......................48 Can I install Subversion 1.7.x on a Subversion Edge server set up as a TeamForge integration server?.49 Are there any other upgrades I need to consider when upgrading to Subversion 1.7.x? ..................................................................................................................................................49 Can I install Subversion 1.7.x on a Subversion Edge server set up as a TeamForge replica server?.49 Subversion Edge REST API...............................................................................................50 General usage.........................................................................................................................................50 Subversion Edge User API.....................................................................................................................52 Subversion Edge User Roles API...........................................................................................................53 Subversion Edge Repository API...........................................................................................................54
Load more

Recommended publications
  • Pragmatic Version Control Using Subversion
    What readers are saying about Pragmatic Version Control using Subversion I expected a lot, but you surprised me with even more. Hav- ing used CVS for years I hesitated to try Subversion until now, although I knew it would solve many of the shortcom- ings of CVS. After reading your book, my excuses to stay with CVS disappeared. Oh, and coming from the Pragmatic Bookshelf this book is fun to read too. Thanks Mike. Steffen Gemkow Managing Director, ObjectFab GmbH I’m a long-time user of CVS and I’ve been skeptical of Sub- version, wondering if it would ever be “ready for prime time.” Until now. Thanks to Mike Mason for writing a clear, con- cise, gentle introduction to this new tool. After reading this book, I’m actually excited about the possibilities for version control that Subversion brings to the table. David Rupp Senior Software Engineer, Great-West Life & Annuity This was exactly the Subversion book I was waiting for. As a long-time Perforce and CVS user and administrator, and in my role as an agile tools coach, I wanted a compact book that told me just what I needed to know. This is it. Within a couple of hours I was up and running against remote Subversion servers, and setting up my own local servers too. Mike uses a lot of command-line examples to guide the reader, and as a Windows user I was worried at first. My fears were unfounded though—Mike’s examples were so clear that I think I’ll stick to using the command line from now on! I thoroughly recommend this book to anyone getting started using or administering Subversion.
    [Show full text]
  • Software Best Practices
    Software Best Practices Marco Mambelli – [email protected] Engineering Week 17 February 2020 Software • Set of instructions and its associated documentations that tells a computer what to do or how to perform a task • Any manuscript/artifact/product written by you with the scope to be used by machine and humans 2 2/17/20 Marco Mambelli | Software best practices 3 2/17/20 Marco Mambelli | Software best practices Outline • General applicability, more in detail – Version control and Git – Documentation • More specific to coding – Requirements – Design • Technology selection • OS Requirements • Software inputs • Software logs, metrics and accounting – Code development – Validation and testing – Releases – Deployment – Bug tracking – Change management – Critical services operation 4 2/17/20 Marco Mambelli | Software best practices “Piled Higher and Deeper” by Jorge Cham, http://www.phdcomics.com 5 2/17/20 Marco Mambelli | Software best practices Version Control System • Preserves different version of a document • Helps merging different contributions • Answers important questions on the documents – What changed? – Who changed it? – Why? 6 2/17/20 Marco Mambelli | Software best practices Centralized vs distributed VCS 7 2/17/20 Marco Mambelli | Software best practices Common RCS • SVN (Apache Subversion) – Newer system based on CVS – Includes atomic operations – Cheaper branch operations, slower comparative speed – Does not use peer-to-peer model – Still contains bugs relating to renaming files and directories – Insufficient repository management
    [Show full text]
  • IPS Signature Release Note V9.17.79
    SOPHOS IPS Signature Update Release Notes Version : 9.17.79 Release Date : 19th January 2020 IPS Signature Update Release Information Upgrade Applicable on IPS Signature Release Version 9.17.78 CR250i, CR300i, CR500i-4P, CR500i-6P, CR500i-8P, CR500ia, CR500ia-RP, CR500ia1F, CR500ia10F, CR750ia, CR750ia1F, CR750ia10F, CR1000i-11P, CR1000i-12P, CR1000ia, CR1000ia10F, CR1500i-11P, CR1500i-12P, CR1500ia, CR1500ia10F Sophos Appliance Models CR25iNG, CR25iNG-6P, CR35iNG, CR50iNG, CR100iNG, CR200iNG/XP, CR300iNG/XP, CR500iNG- XP, CR750iNG-XP, CR2500iNG, CR25wiNG, CR25wiNG-6P, CR35wiNG, CRiV1C, CRiV2C, CRiV4C, CRiV8C, CRiV12C, XG85 to XG450, SG105 to SG650 Upgrade Information Upgrade type: Automatic Compatibility Annotations: None Introduction The Release Note document for IPS Signature Database Version 9.17.79 includes support for the new signatures. The following sections describe the release in detail. New IPS Signatures The Sophos Intrusion Prevention System shields the network from known attacks by matching the network traffic against the signatures in the IPS Signature Database. These signatures are developed to significantly increase detection performance and reduce the false alarms. Report false positives at [email protected], along with the application details. January 2020 Page 2 of 245 IPS Signature Update This IPS Release includes Two Thousand, Seven Hundred and Sixty Two(2762) signatures to address One Thousand, Nine Hundred and Thirty Eight(1938) vulnerabilities. New signatures are added for the following vulnerabilities: Name CVE–ID
    [Show full text]
  • Trabajo De Fin De Carrera
    TRABAJO DE FIN DE CARRERA TÍTULO DEL TFC: VirtualEPSC, el mundo virtual 2.0 del Campus del Baix Llobregat TITULACIÓN: Ingeniería Técnica de Telecomunicación, especialidad en Telemática AUTORES: Luis Miguel Amorós Martínez Noemí Arbós Linio DIRECTOR: Toni Oller Arcas FECHA: 14 de julio de 2010 Título: VirtualEPSC, el mundo virtual 2.0 del Campus del Baix Llobregat Autores: Luis Miguel Amorós Martínez Noemí Arbós Linio Director: Toni Oller Arcas Fecha: 14 de julio de 2010 Resumen En las últimas décadas, se han producido cambios tecnológicos de gran envergadura que han provocado una ruptura brusca con las tecnologías existentes hasta el momento. Una de las más importantes es Internet, que se ha convertido en el entorno de comunicación más importante de la historia, con más de mil millones de usuarios en todo el mundo. Internet ha sufrido una serie de cambios en los últimos años y uno de los últimos conceptos que han surgido es el de web 2.0. Esta filosofía se basa en dar un rol más activo a los usuarios, por ejemplo, utilizando la colaboración de los usuarios en Internet, también llamado inteligencia colectiva; y en el diseño centrado en el usuario. Este trabajo describe los pasos seguidos para desarrollar una web 2.0 que aloja un mundo virtual que emula el Campus del Baix Llobregat. Se describe cómo son el diseño y la arquitectura del proyecto, y cómo se ha hecho la implementación de las diferentes partes. El resultado se denomina VirtualEPSC, una web 2.0 que aloja una aplicación multimedia en 2D que emula el Campus del Baix Llobregat, donde los usuarios podrán interactuar entre ellos.
    [Show full text]
  • Open Source Used in Personnel 0.501
    Open Source Used In personnel 0.501 Cisco Systems, Inc. www.cisco.com Cisco has more than 200 offices worldwide. Addresses, phone numbers, and fax numbers are listed on the Cisco website at www.cisco.com/go/offices. Text Part Number: 78EE117C99-172189840 Open Source Used In personnel 0.501 1 This document contains licenses and notices for open source software used in this product. With respect to the free/open source software listed in this document, if you have any questions or wish to receive a copy of any source code to which you may be entitled under the applicable free/open source license(s) (such as the GNU Lesser/General Public License), please contact us at [email protected]. In your requests please include the following reference number 78EE117C99-172189840 Contents 1.1 aiocontextvars 0.2.0 1.1.1 Available under license 1.2 aiohttp 3.4.4 1.2.1 Available under license 1.3 aiohttp_cors 0.7.0 1.3.1 Available under license 1.4 alabaster 0.7.12 1.4.1 Available under license 1.5 amqp 2.3.2 1.5.1 Available under license 1.6 argh 0.26.2 1.7 arrow 0.8.0 1.7.1 Available under license 1.8 asn1crypto 0.24.0 1.8.1 Available under license 1.9 async-timeout 3.0.1 1.9.1 Available under license 1.10 attrs 18.2.0 1.10.1 Available under license 1.11 avro-python3 1.8.2 1.11.1 Available under license 1.12 Babel 2.6.0 1.12.1 Available under license 1.13 billiard 3.5.0.4 1.13.1 Available under license 1.14 bleach 3.0.2 Open Source Used In personnel 0.501 2 1.14.1 Available under license 1.15 boto3 1.5.15 1.15.1 Available under
    [Show full text]
  • Inequalities in Open Source Software Development: Analysis of Contributor’S Commits in Apache Software Foundation Projects
    RESEARCH ARTICLE Inequalities in Open Source Software Development: Analysis of Contributor’s Commits in Apache Software Foundation Projects Tadeusz Chełkowski1☯, Peter Gloor2☯*, Dariusz Jemielniak3☯ 1 Kozminski University, Warsaw, Poland, 2 Massachusetts Institute of Technology, Center for Cognitive Intelligence, Cambridge, Massachusetts, United States of America, 3 Kozminski University, New Research on Digital Societies (NeRDS) group, Warsaw, Poland ☯ These authors contributed equally to this work. * [email protected] a11111 Abstract While researchers are becoming increasingly interested in studying OSS phenomenon, there is still a small number of studies analyzing larger samples of projects investigating the structure of activities among OSS developers. The significant amount of information that OPEN ACCESS has been gathered in the publicly available open-source software repositories and mailing- list archives offers an opportunity to analyze projects structures and participant involve- Citation: Chełkowski T, Gloor P, Jemielniak D (2016) Inequalities in Open Source Software Development: ment. In this article, using on commits data from 263 Apache projects repositories (nearly Analysis of Contributor’s Commits in Apache all), we show that although OSS development is often described as collaborative, but it in Software Foundation Projects. PLoS ONE 11(4): fact predominantly relies on radically solitary input and individual, non-collaborative contri- e0152976. doi:10.1371/journal.pone.0152976 butions. We also show, in the first published study of this magnitude, that the engagement Editor: Christophe Antoniewski, CNRS UMR7622 & of contributors is based on a power-law distribution. University Paris 6 Pierre-et-Marie-Curie, FRANCE Received: December 15, 2015 Accepted: March 22, 2016 Published: April 20, 2016 Copyright: © 2016 Chełkowski et al.
    [Show full text]
  • Python Programming Language
    ภาษาโปรแกรมมิ่งไพธอน Python programming language เอกวิทยาการคอมพิวเตอรì คณะวิทยาศาสตรì มหาวิทยาลัยนเรศวร 2 รายชื่อผูéจัดทำ ชื่อ รหัสนิสิต หนéาที่ดำเนินการ นายฉัตรชัย ดำดี 46320388 แบบฝกหัด นายทรงยศ คชนิล 46320511 จัดทำเอกสารการเรียน นางสาวธัญญากร แกéวประสงคì 46320610 ผูéชèวยสอน นายประจักษì เจตะภัย 46320693 ผูéชèวยสอนและแบบฝกหัด นายมารุต จันทรìบัว 46320818 แบบฝกหัด นางสาวศรินยา อยูèสุขดี 46320925 ผูéชèวยสอน นางสาวณัฐณิชา คงประกอบ 46321097 ผูéชèวยสอน นายอุทิศ ศักดิ์สิทธิ์ 46321139 ผูéชèวยสอนและแบบฝกหัด นายอรรณพ สุวัฒนพิเศษ 46321150 ผูéสอนและจัดทำเอกสารเรียน 3 4 คำนำ ภาษาไพธอนเปนภาษาที่ไดéรับความนิยมอยèางมากในปจจุบันเนื่องจากความสามารถที่สูง, การเรียนรูéที่ รวดเร็ว, การเขียนระบบที่เขéาใจงèาย และสามารถขยายขีดความสามารถในการสรéางโปรแกรมและซอฟตìแวรì ที่สูงมากขึ้นตลอดเวลา ทางทีมผูéจัดทำจึงเล็งเห็นวèาควรนำความรูé ความเขéาใจในการเขียนโปรแกรมดéวยภาษา ไพธอนมาเผยแพรè ดéวยจะไดéผูéอื่นไดéรับความรูéและไดéเขéาถึงภาษาที่เขียนใจงèาย, ทำงานรวดเร็ว และสามารถ สรéางสรรคìงานไดéอยèางมีความสามารถสูง อีกทั้งซอฟตìแวรìที่ใชéสรéางโปรแกรมและซอฟตìแวรìดéวยภาษาไพธอน นั้นมีทั้งแจกฟรี, รหัสเปด และเชิงธุรกิจ ซึ่งมีขีดความสามารถที่แตกตèางกัน แตèถึงแมéจะเปนซอฟตìแวรìที่ใชé เขียนโปรแกรมดéวยภาษาไพธอนจะแจกฟรี หรือเปนรหัสเปด ก็ไมèไดéดéอยไปกวèาเชิงธุรกิจเลย จึงเปนทางเลือก ที่ดีที่จะศึกษาเปนทางเลือกอีกทางหนึ่งนอกเหนือจากภาษาอื่น ๆ ที่ไดéรับความนิยมอยูèแลéว ทางทีมงานจึงหวังวèาทèานผูéที่นำเอกสารนี้ไปใชéในการศึกษาจะไดéรับประโยชนìสูงสุดในการเขียนโปรแกรม และซอฟตìแวรìดéวยภาษาไพธอน ทีมผูéจัดทำ 5 6 สารบัญ 1 แนะนำภาษาไพธอน 13 1.1 ประวัติ . 13 1.1.1 Python 1.0 . 13 1.1.2 Python 2.0 . 14 1.1.3
    [Show full text]
  • Collaboration Tools in Software Engineering Stepan Bolotnikov Me
    Collaboration Tools in Software Engineering Stepan Bolotnikov Me ● Stepan Bolotnikov ● Software Engineer at Guardtime ● MSc in Software Engineering from UT, 2018 ● [email protected] You Mostly BSc students in Computer Science ● Software developers / QA engineers ● CS researchers ● Project managers / team leads In any case connected to software projects, sharing knowledge and resources Course ● History and working principles of version control systems (VCS) ● Git distributed VCS ● Issue tracking ● Theoretical knowledge + practical hands-on exercises ● 8 sessions ● Every 2nd Friday ● Lecture + practice ● Non-differentiated (pass/fail) Schedule ● 22. Feb - Introduction, history of VCS ● 08. Mar - Introduction to Git, setting up the first repository, basic Git usage ● 22. Mar - Common Git commands ● 05. Apr - Branching in Git, common branching models ● 19. Apr - Troubleshooting common Git issues ● 03. May - Github; Issue tracking ● 17. May - Advanced Git usage; git hooks and CI ● 31. May - Guest lecture, preparation for exam ● 07. June - Exam 1 ● 14. June - Exam 2 Sessions ● 4h ● Lecture part ● Practical part Final exam ● 7th or 17th June ● Individual practical tasks ● “Poor”, “Satisfactory” or “Good” ● “Satisfactory” and “Good” - passing In order to pass the course ● Active participation in at least 6 out of 8 sessions ○ Complete the practical tasks ● “Satisfactory” or “Good” on the final exam Communication Course website http://courses.cs.ut.ee/2019/cse Course Slack Click Lecture 1: Introduction to course, History of Version
    [Show full text]
  • CPS Release Notes
    Release Notes for Cisco Policy Suite for Release 7.0 First Published: September 26, 2014 Last Updated: July 10, 2015 Release: 7.0 Contents This document describes the new features, feature versions and limitations for the Cisco Policy Suite software. Use this document in combination with documents listed in the “Related Documentation” section on page 33. This document includes the following sections: • Introduction, page 1 • New and Changed Information, page 2 • Installation Notes, page 9 • Limitations and Restrictions, page 15 • Caveats, page 23 • Related Documentation, page 33 Introduction The Cisco Policy Suite is a comprehensive policy, charging, and subscriber data management solution that allows service providers to control and monetize their networks and to profit from personalized services. The Cisco Policy Suite has the following components: • Policy Server (PS) • Charging Server (CS) • Application Gateway (AGW) Cisco Systems, Inc. www.cisco.com New and Changed Information • Unified Subscriber Manager (USuM) • Subscriber Analytics The Cisco Policy Suite provides an intelligent control plane solution, including southbound interfaces to various policy control enforcement functions (PCEFs) in the network, and northbound interfaces to OSS/BSS and subscriber applications, IMSs, and web applications. The Cisco Policy Suite modules are enabled individually or deployed as an integrated end-to-end policy, charging, and service creation solution. Competitive Benefits The new Cisco Policy Suite solution provides these benefits over competitive solutions. • Cisco Policy Suite architecture allows simultaneous sessions and transactions per second (TPS) capacity to be independently scaled. This allows Cisco Policy Suite to be efficiently sized for both high simultaneous sessions with low TPS or low sessions with high TPS, resulting in lower total cost of ownership when compared to traditional PCRF models.
    [Show full text]
  • Design Options of Store-Oriented Software Ecosystems: an Investigation of Business Decisions ∗
    Design Options of Store-Oriented Software Ecosystems: An Investigation of Business Decisions ∗ Bahar Jazayeri1, Olaf Zimmermann2, Gregor Engels1, Jochen K¨uster3, Dennis Kundisch1, Daniel Szopinski1 1 Paderborn University, Germany fbahar.jazayeri,gregor.engels,dennis.kundisch,[email protected] 2 University of Applied Sciences of Eastern Switzerland, Switzerland [email protected] 3 Bielefeld University of Applied Sciences, Germany [email protected] Abstract. Nowadays companies like Apple create ecosystems of third- party providers and users around their software platforms. Often online stores like Apple App Store are created to directly market third-party solutions. We call such ecosystems store-oriented software ecosystems. While the architecture of these ecosystems is mainly derived from busi- ness decisions of their owners, ecosystems with greatly different archi- tectural designs have been created. This diversity makes it challenging for future ecosystem providers to understand which architectural design is suitable to fulfill certain business decisions. In turn, opening a plat- form becomes risky while endangering intellectual property or scarifying quality of services. In this paper, we identify three main design options of store-oriented software ecosystems by classifying existing ecosystems based on similarities in their business decisions. We elaborate on the design options, discuss their main contributions, and provide exemplary ecosystems. Our work provides aspiring ecosystem providers with the reusable knowledge of existing ecosystems and helps them to take more informed architectural decisions and reduce risks in future. Keywords: Software ecosystems, Reusable designs, Variabilities 1 Introduction Software ecosystems have become an emerging architectural approach for many companies to grow. The term software ecosystem is inspired from ecological ecosystems that are the result of an interplay between organisms as well as interactions with a physical environment [1].
    [Show full text]
  • Cross-Platform Environment for Application Life Cycle Management
    International Journal “Information Theories and Applications”, Vol. 24, Number 2, © 2017 177 CROSS-PLATFORM ENVIRONMENT FOR APPLICATION LIFE CYCLE MANAGEMENT Elena Chebanyuk, Oleksii Hlukhov Abstract: “Application Lifecycle Management (ALM) integrates and governs the planning, definition, design, development, testing, deployment, and management phases throughout the application lifecycle” [OMG, 2006]. This paper is devoted to designing of ALM for supporting all software development processes. A review of papers, making strong contribution for improving software development life cycle processes is represented. This review touches three branches of investigation, namely papers, related to: (1) improving of communication processes between stakeholders; (2) increasing effectiveness of some operations in software development life cycle processes; (3) developing fundamental methods and tools for performing different operations related to several software development life cycle. Then comparative analysis of such ALM environments as Visual Studio, Team Foundation Server, FusionForge, TeamForge, IBM Rational Team Concert, IBM Rational Software Architect, and IBM Rational Functional Tester, is performed. Comparison of different ALM environments’ functionality lets to formulate requirements for designing cross-platform ALM environment. Then the conceptual schema of cross-platform ALM based on Eclipse environment is proposed. All plugins’ functionalities were properly tested. Collaboration of plugins for supporting several software development tasks
    [Show full text]
  • Documentation for Fisheye 2.8 Documentation for Fisheye 2.8 2
    Documentation for FishEye 2.8 Documentation for FishEye 2.8 2 Contents Getting started . 8 Supported platforms . 8 End of Support Announcements for FishEye . 12 End of Support Announcement for IBM ClearCase . 14 End of Support Announcement for Internally Managed Repositories . 14 Installing FishEye on Windows . 16 Running FishEye as a Windows service . 19 Installing FishEye on Linux and Mac . 23 Starting to use FishEye . 26 Configuring JIRA Integration in the Setup Wizard . 31 Using FishEye . 38 Using the FishEye Screens . 39 Browsing through a repository . 41 Searching FishEye . 44 Viewing a File . 49 Viewing File Content . 50 Using Side by Side Diff View . 51 Viewing a File History . 53 Viewing the Changelog . 54 FishEye Charts . 56 Using Favourites in FishEye . 61 Changeset Discussions . 64 Viewing the commit graph for a repository . 64 Viewing People's Statistics . 68 Using smart commits . 70 Changing your User Profile . 75 Re-setting your password . 79 Antglob Reference Guide . 80 Date Expressions Reference Guide . 81 EyeQL Reference Guide . 82 Administering FishEye . 88 Managing your repositories . 89 Adding an External Repository . 91 CVS . 92 Git . 93 Mercurial . 96 Perforce . 98 Subversion . 101 SVN fisheye.access . 105 SVN tag and branch structure . 106 Adding an Internal Repository . 114 Enabling Repository Management in FishEye . 115 Creating Git Repositories . 117 Forking Git Repositories . 119 Deleting a Git Repository . 122 Setting up a Repository Client . 122 CVS Client . 122 Git Client . 122 Mercurial Client . 122 Perforce Client . 123 Subversion Client . 124 Native Subversion Client . 124 SVNkit Client . 126 Re-indexing your Repository . 126 Repository Options . 128 Authentication . 130 Created by Atlassian in 2012.
    [Show full text]