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

vcsh

  • Clone with SSH
  • Clone with HTTPS
  • user avatar
    Dato Simó authored
    `vcsh clone` does:
    
        VCSH_REPO_NAME=$(basename "${GIT_REMOTE}" .git)
    
    Typically, most remote paths will have a non-empty directory component,
    so using basename works well in all common cases. However, when doing
    something like:
    
        % vcsh clone example.org:repo.git
    
    VCSH_REPO_NAME will be set to "example.org:repo" instead of "repo". This
    also happens when using url.<x>.insteadOf, à-la:
    
        % vcsh clone v:repo
    
    Stripping everything up to the first colon in the remote URL fixes the
    issue.
    
    N.B.: remote URLs with protocol (e.g. http://, git://, or ssh://) do
    not exhibit this problem, and are unaffected by this change.
    
    Conflicts:
    	vcsh
    b4bee06a
    History
    Name Last commit Last update