<div dir="ltr"><div><div><div><div>Hi Andrew,<br><br><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote">On Fri, Jan 30, 2015 at 8:17 PM, Andrew Gwozdziewycz <span dir="ltr"><<a href="mailto:web@apgwoz.com" target="_blank">web@apgwoz.com</a>></span> wrote:<br><span class="">On Fri, Jan 30, 2015 at 1:14 PM, Jacob Hoffman-Andrews <<a href="mailto:jsha@eff.org">jsha@eff.org</a>> wrote:</span><br><span class="">
</span><span class="">
></span><br><span class="">
> You talk about tracking a subdirectory of the https-everywhere repo. Why</span><br><span class="">
> not instead just track the whole repo and have your proxy's input path</span><br><span class="">
> point at src/chrome/content/rules?</span><br><span class="">
</span><br><span class="">
</span>Yup, that's what I'll do for now. Thanks.<br></blockquote><br></div>found something :)<br><br><a href="http://stackoverflow.com/questions/600079/is-there-any-way-to-clone-a-git-repositorys-sub-directory-only">http://stackoverflow.com/questions/600079/is-there-any-way-to-clone-a-git-repositorys-sub-directory-only</a><br><br></div>Try and take a look at the second answer, the one that mentions "sparse checkout".<br><br></div>AFAIK, you'll still have the entire subtree (src/chrome/content/rules) but you'll be able to checkout the rules only.<br><br></div>Claudio<br><br></div>