1. 20 Jul, 2010 4 commits
  2. 19 Jul, 2010 1 commit
  3. 13 Jul, 2010 3 commits
  4. 12 Jul, 2010 3 commits
  5. 11 Jul, 2010 1 commit
  6. 10 Jul, 2010 1 commit
  7. 09 Jul, 2010 2 commits
  8. 08 Jul, 2010 1 commit
  9. 07 Jul, 2010 5 commits
  10. 05 Jul, 2010 1 commit
  11. 01 Jul, 2010 1 commit
  12. 30 Jun, 2010 1 commit
  13. 29 Jun, 2010 1 commit
    • gavinp@google.com's avatar
      Add explicit file rename/cp information to svn rietveld uploads · 3fda4cce
      gavinp@google.com authored
      Right now if you svn cp or svn mv before uploading to rietveld,
      there's no description in the patch at all of what was done; so you
      get a diff, but it's for who knows what revision of what prior file
      to some current version.
      
      For code reviews this kinda works (you ask the guy what it was), but for
      trying to apply patches (ala git patch) this fails badly.  This patch
      tries to add some metadata to the start of a rietveld patch that
      describes these changes: both to a human (who can read them)
      and to a potential clever future git-cl (which I'll do next).
      
      The metadata looks like this after checking out a test repo, and
      svn cp -r 1 foo nitz; svn cp bar quux; echo be good>>quux
      
        ### BEGIN SVN COPY METADATA
        #$ svn cp -r 1 foo nitz ### WARNING: note non-trunk copy
        #$ cp bar quux
        ### END SVN COPY METADATA
        Index: nitz
        Index: quux
        ===================================================================
        --- quux	(revision 0)
        +++ quux	(working copy)
        @@ -1,2 +1,3 @@
         hi mom
         hi sister
        +be good
      
      I did a test, and this looks like it works in svn 1.4.4 as well.
      
      BUG=none
      TEST=none
      Review URL: http://codereview.chromium.org/2824035
      
      git-svn-id: svn://svn.chromium.org/chrome/trunk/tools/depot_tools@51121 0039d316-1c4b-4281-b951-d872f2087c98
      3fda4cce
  14. 28 Jun, 2010 2 commits
  15. 23 Jun, 2010 1 commit
  16. 22 Jun, 2010 1 commit
  17. 21 Jun, 2010 2 commits
  18. 18 Jun, 2010 4 commits
  19. 17 Jun, 2010 2 commits
  20. 16 Jun, 2010 3 commits