Skip to content
Permalink
Branch: git-crypt-supp…
Commits on Feb 14, 2016
  1. Work-In-Progress: Add support for `git-crypt`

    TheLocehiliosan committed Feb 14, 2016
    `git-crypt` is a tool which can encrypt data within a Git repository.
    
    https://github.com/AGWA/git-crypt
    
    Notes:
      * All `git-crypt` commands can be passed through `yadm`
      * `init` and `status` must be prefaced with `crypt-` because those
        commands are already used by `yadm`.
      * Any FILE specified by the `unlock` command should be fully
        qualified. This is because under-the-hood `git-crypt` must be
        executed relative to the git WORK TREE.
      * Care should be taken to add any `.gitattributes` files to the `yadm`
        repository.
      * `git-crypt status` seems to be very slow if the working tree has
        many files (as most `$HOME` directories do).
    
    Not Done:
      * `yadm` should restrict the permissions for any files which are
        encrypted with `git-crypt`. Right now I think the only possible way
        is to run `git-crypt status -e` to determine which files need this
        treatment, but `git-crypt status` runs very slowly when the work
        tree has lots of files.
Commits on Feb 13, 2016
  1. Translate gitconfig to config inside git_command()

    TheLocehiliosan committed Feb 13, 2016
    This consolidates calls to git_command()
Commits on Jan 22, 2016
  1. Rebuild CONTRIBUTORS

    TheLocehiliosan committed Jan 22, 2016
  2. Merge pull request #2 from kosciak9/master

    TheLocehiliosan committed Jan 22, 2016
    Add information about AUR package
  3. I've made AUR package for yadm, so I've

    kosciak9 committed Jan 22, 2016
    updated README to reflect it
Commits on Jan 9, 2016
  1. Release 1.03

    TheLocehiliosan committed Jan 9, 2016
    Update version number and update documentation
  2. Add CONTRIBUTORS

    TheLocehiliosan committed Jan 9, 2016
Commits on Dec 17, 2015
Commits on Dec 16, 2015
  1. Added username matching for alternate files

    Patrick Hof
    Patrick Hof committed Dec 16, 2015
Commits on Sep 10, 2015
Commits on Sep 8, 2015
Commits on Aug 29, 2015
  1. Use em-dashes properly

    TheLocehiliosan committed Aug 29, 2015
    I only recently learned the difference between hyphen, en-dash,
    em-dash, minus, etc.
Commits on Aug 12, 2015
  1. Release 1.02

    TheLocehiliosan committed Aug 12, 2015
    Update version number and update documentation
Commits on Aug 7, 2015
  1. Handle permissions for `~/.gnupg/*gpg`

    TheLocehiliosan committed Aug 7, 2015
    By default, gpg keyrings and configurations will have their permissions
    locked down. The option `yadm.gpg-perms` can be used to disable.
Commits on Jul 26, 2015
  1. Release 1.01

    TheLocehiliosan committed Jul 26, 2015
    Update version number and update documentation
  2. Set `status.showUntrackedFiles` to "no"

    TheLocehiliosan committed Jul 26, 2015
    Each time the yadm repository is initialized or cloned,
    set `status.showUntrackedFiles` to "no". This prevents untracked files
    and directories from showing up in status commands. This seems to be the
    most sensible default, because usually there will be MANY untracked
    files in a user's $HOME directory.
Commits on Jul 21, 2015
Commits on Jul 20, 2015
  1. Add installation info

    TheLocehiliosan committed Jul 20, 2015
Commits on Jul 19, 2015
  1. Refine documentation

    TheLocehiliosan committed Jul 19, 2015
  2. Add a default alternate suffix of `##`

    TheLocehiliosan committed Jul 19, 2015
    Now yadm chooses these three suffixes in order:
     - `##SYSTEM.HOSTNAME`
     - `##SYSTEM`
     - `##`
Commits on Jul 17, 2015
  1. Change `==` to `=`

    TheLocehiliosan committed Jul 17, 2015
Commits on Jul 16, 2015
Commits on Jul 14, 2015
  1. Confirm targets exist before linking

    TheLocehiliosan committed Jul 14, 2015
    Targets *might* exist in Git, but not in the work tree.
    (especially when initially cloning)
Older
You can’t perform that action at this time.