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
  • Kevin Lyda's avatar
    Kevin Lyda authored
    For vcsh commands that loop through repos, hooks were not
    run correctly. Typically what would be run were:
    
      pre-looping-hook*
      .pre-looping-hook*
      [command run on repo r1, r2, r3 ... rN]
      post-looping-hook*
      rN.post-looping-hook
    
    The new, more obvious behaviour is:
    
      pre-looping-hook*
      r1.pre-looping-hook*
      [command run on repo r1]
      r1.post-looping-hook
      [...]
      rN.pre-looping-hook*
      [command run on repo r1]
      rN.post-looping-hook
      post-looping-hook*
    
    I was mainly concerned with the pull command, but I've made changes
    in all "for VCSH_REPO_NAME" loops. This is my way of resolving
    issue RichiH/vcsh#213, but as I note there are other options.
    0716528b
    History
    Name Last commit Last update