Re: [webkit-dev] WebKit project repo size

Also, removing files from the repo does not save anything with a Git checkout since they are still there in the history. — Timothy Hatcher > On Mar 31, 2016, at 12:50 PM, Brian Burg wrote: > > Hi Marcus, > > It’s unclear what your actual problem is. > > If you have trouble downloading

Re: [webkit-dev] WebKit project repo size

On Thu, Mar 31, 2016 at 12:42 PM, Marcus Johnson wrote: > I use the git mirror, so I'm not sure how large the main SVN repo is, but > the git one is huge at like 7 GB. > > I think the best way to reduce that amount of space, is by splitting out the > websites into their own repos, and possibly eve

Re: [webkit-dev] WebKit project repo size

Hi Marcus, It’s unclear what your actual problem is. If you have trouble downloading 7GB at once due to a slow or flaky connection, you can fetch earlier git commits to finish the initial repository checkout, and then fetch more commits in batches. If you just want a subset of the repos

[webkit-dev] WebKit project repo size

I use the git mirror, so I'm not sure how large the main SVN repo is, but the git one is huge at like 7 GB. I think the best way to reduce that amount of space, is by splitting out the websites into their own repos, and possibly even the unit tests into their own repo as well. Also, I've had pret

Re: [webkit-dev] Suggestion: runtime disable Fetch API until it's complete enough for real web-apps

> On Mar 31, 2016, at 11:14 AM, youenn fablet wrote: > > Hi, > > I like the idea of a runtime flag. > I would wait to enable fetch use until it passes sufficient numbers of > web-platform-test tests. > This can be tested in http://w3c-test.org/tools/runner/index.html >

Re: [webkit-dev] Suggestion: runtime disable Fetch API until it's complete enough for real web-apps

Woups, the mail went out too fast. Fetch API is not yet supporting some options like CORS at the moment. I think we should expose fetch once it is using properly all existing ThreadableLoader options. y Le jeu. 31 mars 2016 à 20:14, youenn fablet a écrit : > Hi, > > I like the idea of a runt

Re: [webkit-dev] Suggestion: runtime disable Fetch API until it's complete enough for real web-apps

Hi, I like the idea of a runtime flag. I would wait to enable fetch use until it passes sufficient numbers of web-platform-test tests. This can be tested in http://w3c-test.org/tools/runner/index.html (folder fetch/api). I think th Also, are you suggesting that it would be in addition to the comp

Re: [webkit-dev] Suggestion: runtime disable Fetch API until it's complete enough for real web-apps

> On Mar 31, 2016, at 10:02 AM, Maciej Stachowiak wrote: > > The recently released Safari Technology Preview has gotten more people living > on builds close to trunk, which is cool. Some people pointing out that the > current state of Fetch API causes problems - it's not quite complete enough

Re: [webkit-dev] Suggestion: runtime disable Fetch API until it's complete enough for real web-apps

+1 Geoff > On Mar 31, 2016, at 10:02 AM, Maciej Stachowiak wrote: > > > The recently released Safari Technology Preview has gotten more people living > on builds close to trunk, which is cool. Some people pointing out that the > current state of Fetch API causes problems - it's not quite com

[webkit-dev] Suggestion: runtime disable Fetch API until it's complete enough for real web-apps

The recently released Safari Technology Preview has gotten more people living on builds close to trunk, which is cool. Some people pointing out that the current state of Fetch API causes problems - it's not quite complete enough for real web apps that want to use it, but its presence breaks the