[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [elpa] New package: vc-got

From: Jean Louis
Subject: Re: [elpa] New package: vc-got
Date: Sun, 17 Oct 2021 07:57:42 +0300
User-agent: Mutt/2.0.7+183 (3d24855) (2021-05-28)

* Eli Zaretskii <eliz@gnu.org> [2021-08-31 17:06]:
> How about keeping it out of vc-handled-backends, so that people who
> want could replace Git with Got?

Git and Got are different VCS systems. Once can understand its
goals by reading the reference:


Project guidelines

- Follow OpenBSD's security practices and coding style.
  - Use a development process based on code review in email.
  - Consistently use pledge(2) and unveil(2) across the code base.
  - Use privilege-separation when parsing repository data from network or disk. 
- Keep the entire code base BSD-licenced. 

Long-term goals

    Remain on-disk compatible with bare Git repositories.
        Don't insist on Git-compatibility beyond this requirement. 
    Provide a complete version control tool suite for OpenBSD.
        Intuitive command line interface for required version control 
operations (got).
        Interactive repository browser for history analysis and review of 
committed changes (tog).
        CGI repository browser for web servers (gotweb).
        Repository administration tooling with a strong focus on backup and 
recovery (gotadmin).
        Repository server for hosting a central repository and synchronizing 
changes to a cascade of public and private mirrors. 
    Consider workflow requirements of OpenBSD developers.
        Strong built-in support for a centralized repository model (ideas about 
        Keep things easy for developers who don't need branches.
        Support local branches for developers who need them.
        Support "-stable" release branches.
        Support features required by the OpenBSD project's build 
    Implement authenticated and encrypted network communications.
        Provide SSH and optional TLS support for cloning repositories and 
pulling changes.
        Exclusively rely on SSH for pushing changes.
        Do not implement server-side support for plaintext network 


Take action in Free Software Foundation campaigns:

In support of Richard M. Stallman

reply via email to

[Prev in Thread] Current Thread [Next in Thread]