1. 28 Jan, 2011 1 commit
  2. 27 Jan, 2011 3 commits
  3. 26 Jan, 2011 1 commit
  4. 25 Jan, 2011 1 commit
  5. 18 Jan, 2011 1 commit
    • mig5's avatar
      Do not send delete = TRUE to the drush rsync call even if no-delete · ad0ca56a
      mig5 authored
      isset. Send it only if no-delete is not set.
      This still leaves delete = TRUE as the default, unless no-delete has been set
      to TRUE. This solves critical bug #976300.
      I can't imagine a case where someone would want to set no-delete = FALSE if
      --delete is the default at all other times, but I added a condition to account
      for this too.
  6. 10 Jan, 2011 3 commits
  7. 04 Jan, 2011 3 commits
  8. 30 Dec, 2010 1 commit
  9. 22 Dec, 2010 3 commits
  10. 21 Dec, 2010 1 commit
  11. 20 Dec, 2010 13 commits
  12. 12 Dec, 2010 1 commit
  13. 10 Dec, 2010 2 commits
    • anarcat's avatar
      do not attempt to chown files/ dir during verification · 98fb236f
      anarcat authored
      the rationale here is that we're not running as root, and therefore
      chown is likely to fail, unless the file already has the right owner,
      in which case a chown is not necessary.
      To quote chown(2):
             Only a privileged process (Linux: one with the CAP_CHOWN
             capability) may change the owner of a file.  The owner of a
             file may change the group of the file to any group of which
             that owner is a member.  A privileged process (Linux: with
             CAP_CHOWN) may change the group arbitrarily.
      So this was just a cause of trouble without any possible benefit
      unless we run with capabilities, and we shouldn't assume this (right
    • mig5's avatar
      #994212 update the README.txt · 95239c4e
      mig5 authored
  14. 06 Dec, 2010 1 commit
  15. 26 Nov, 2010 1 commit
    • anarcat's avatar
      add a command to parse --backend output · d6477f6b
      anarcat authored
      i got tired of stabbing my eyes with inline JSON output so I wrote a
      very very simple command that just parses STDIN as a --backend output
      command. this can be useful for debugging when calling backend commands
      without thinking of removing --backend, or in my case, to pass data
      through STDIN as JSON, but still have a proper output.
  16. 22 Nov, 2010 4 commits