Skip to content
Snippets Groups Projects
Select Git revision
  • 273818ae7a5a9e084ba0a26e182e722ab95250fe
  • master default protected
  • commit-alias
  • editor-modeline
  • commit-abbreviation
  • make-hooks-work-as-advertised
  • lyda-home-version
  • 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
30 results

100-init.t

  • Thomas Tuegel's avatar
    12d208c2
    Do not use shared Git repositories · 12d208c2
    Thomas Tuegel authored
    Shared repositories were created using `git init --shared=0600` with the intent
    of keeping configuration data private. Git reports an error if "shared"
    repositories are created with private permissions. (Due to an apparent bug, the
    error was not reported before git-2.13.2.)
    
    Instead of creating a shared repository, use `umask 0077` to make created files
    accessible only to the current user. The umask setting is inherited by child
    processes and respected by Git.
    Do not use shared Git repositories
    Thomas Tuegel authored
    Shared repositories were created using `git init --shared=0600` with the intent
    of keeping configuration data private. Git reports an error if "shared"
    repositories are created with private permissions. (Due to an apparent bug, the
    error was not reported before git-2.13.2.)
    
    Instead of creating a shared repository, use `umask 0077` to make created files
    accessible only to the current user. The umask setting is inherited by child
    processes and respected by Git.