Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Bringing in the latest Sizzle code. | jeresig | 2011-04-10 | 1 | -0/+0 |
| | |||||
* | Pulling in latest Sizzle. | jeresig | 2011-04-10 | 1 | -0/+0 |
| | |||||
* | Land new sizzle commit. | jeresig | 2011-03-24 | 1 | -0/+0 |
| | |||||
* | Updating Sizzle submodule to bring in the latest commit. | jeresig | 2011-03-24 | 1 | -0/+0 |
| | |||||
* | Introduce submodules, closes #8536 | Carl Fürstenberg | 2011-03-15 | 1 | -0/+0 |
| | | | | | | Instead of the manual clone of sizzle and qunit, use git submodules instead. this will ensure that all future releases can be recreated by checking out an tag. | ||||
* | Switched from using Git Submodules to just doing a straight clone of the ↵ | jeresig | 2009-11-30 | 1 | -0/+0 |
| | | | | QUnit and Sizzle directories. Works much better for what we want. | ||||
* | Bringing Sizzle and QUnit up to date. | jeresig | 2009-11-30 | 1 | -0/+0 |
| | |||||
* | Pull in the Sizzle library dynamically using a submodule and make it part of ↵ | John Resig | 2009-10-26 | 1 | -0/+0 |
the jQuery build process. |