1. 12 Feb, 2014 1 commit
  2. 16 Jan, 2014 1 commit
  3. 04 Jan, 2014 1 commit
  4. 02 Nov, 2013 1 commit
  5. 21 Jul, 2013 1 commit
  6. 17 May, 2013 1 commit
  7. 30 Apr, 2013 1 commit
  8. 04 Apr, 2013 1 commit
  9. 06 Mar, 2013 1 commit
  10. 21 Feb, 2013 1 commit
  11. 16 Feb, 2013 1 commit
  12. 13 Feb, 2013 1 commit
  13. 28 Jan, 2013 1 commit
  14. 27 Jan, 2013 1 commit
  15. 03 Dec, 2012 1 commit
  16. 02 Nov, 2012 1 commit
  17. 21 Oct, 2012 1 commit
  18. 11 Oct, 2012 1 commit
  19. 06 Oct, 2012 1 commit
  20. 08 Sep, 2012 1 commit
  21. 20 Jul, 2012 1 commit
  22. 13 Jun, 2012 1 commit
  23. 30 Apr, 2012 1 commit
  24. 15 Apr, 2012 1 commit
  25. 18 Dec, 2011 2 commits
  26. 03 Nov, 2011 2 commits
    • mevenson@1c010e3e-69d0-11dd-93a8-456734b0d56f's avatar
      Enable ASDF to load from jar files again for #181. · 8fc258a7
      Unsure if we need to somehow change the semantics of how
      MERGE-PATHNAMES works in the presence of JAR-PATHNAMES.  Currently, we
      have the following behavior:
      
      CL-USER> (merge-pathnames "/home/evenson/work/abcl/dist/abcl-contrib.jar" #p"jar:file:/foo/bar.jar!/fee/")
      #P"jar:file:/foo/bar.jar!/home/evenson/work/abcl/dist/abcl-contrib.jar"
      
      Should we "break" ANSI here, so that if we have a defaulted DEVICE, we
      also keep the defaulted DIRECTORY?  Unfortunately, I think this will
      break some common cases of dealing with relative directories inside a
      JAR-PATHNAME.  Need to consider this with email to both
      @armedbear-develop and @asdf-develop.
      8fc258a7
    • mevenson@1c010e3e-69d0-11dd-93a8-456734b0d56f's avatar
      00ad9ec1
  27. 21 Oct, 2011 1 commit
  28. 27 Jul, 2011 1 commit
  29. 10 Jun, 2011 2 commits
  30. 09 Jun, 2011 2 commits
  31. 08 Jun, 2011 1 commit
  32. 28 Mar, 2011 1 commit
  33. 20 Mar, 2011 1 commit
  34. 05 Jan, 2011 1 commit
  35. 03 Dec, 2010 1 commit
  36. 31 Oct, 2010 1 commit