Skip to content
Snippets Groups Projects
Select Git revision
  • commit-alias
  • editor-modeline
  • commit-abbreviation
  • make-hooks-work-as-advertised
  • lyda-home-version
  • master default protected
  • feature-aliases
  • git-version-bsd-fix
  • hook-changes
  • v1.20151229-1
  • v1.20151229
  • v1.20150502-1
  • v1.20150502
  • v1.20141026-manpage-static
  • v1.20141026-1
  • v1.20141026
  • v1.20141025-1
  • v1.20141025
  • v1.20141009-manpage-static
  • v1.20141009-1
  • v1.20141009
  • v1.20140508-1-bpo70+1
  • v1.20140508-1
  • v1.20140508-manpage-static
  • v1.20140508
  • v1.20140507
  • v1.20140313
  • v1.20131229-homebrew
  • v1.20131229-1-bpo60+1
29 results

README.md

Blame
  • README.md 12.31 KiB

    vcsh - manage config files in $HOME via fake bare git repositories

    Index

    1. Contact
    2. Introduction
    3. Overview
    4. Getting Started
    5. Usage

    1 Contact

    There are several ways to get in touch with the author and a small but committed community around the general idea of version controlling your (digital) life.

    2 Introduction

    vcsh allows you to have several git repositories, all maintaining their working trees in $HOME without clobbering each other. That, in turn, means you can have one repository per config set (zsh, vim, ssh, etc), picking and choosing which configs you want to use on which machine.

    vcsh was designed with [mr] 1 in mind so you might want to install that, as well.

    Read INSTALL.md for detailed setup instructions.