[HTTPS-Everywhere] How can I distinguish between stable and unstable rules?

[James Elford]

But it's
On 8 Feb 2013 19:32, "Robert Picard" <robert at duckduckgo.com> wrote:
>
> Perfect, thanks!
>
> Robert Picard
>
>
> ---- On Fri, 08 Feb 2013 13:19:55 -0500 Seth David Schoen<schoen at eff.org>
wrote ----
>
>> Robert Picard writes:
>>
>> > I'm working on a program that uses the HTTPS Everywhere rulesets. I'd
like to be able to use only
>> > stable rules, but I can't find a way to identify them
programmatically. Somebody pointed out to me that
>> > the Chrome extension separates the two, it makes me think that there
is some mechanism for this, but
>> > I haven't been able to find it in the source.
>> >
>> > I'd appreciate a little insight into this!
>>
>> Hi,
>>
>> This distinction refers to two different git branches in our repository.
>> The stable rules are those in the "stable" git branch, while the
unstable
>> rules are those in the "master" git branch. So if you do
>>
>> git checkout stable
>>
>> in a copy of the HTTPS Everywhere git tree, you'll see the stable rules
>> in src/chrome/content/rules.
>>
>> --
>> Seth Schoen <schoen at eff.org>
>> Senior Staff Technologist https://www.eff.org/
>> Electronic Frontier Foundation https://www.eff.org/join
>> 454 Shotwell Street, San Francisco, CA 94110 +1 415 436 9333 x107
>
>
>
> _______________________________________________
> HTTPS-everywhere mailing list
> HTTPS-everywhere at mail1.eff.org
> https://mail1.eff.org/mailman/listinfo/https-everywhere

But do "stable" and "unstable" branches in HTTPS Everywhere's source tree
necessarily reflect on the stability if the rules themselves - or just the
code...?

James
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.eff.org/pipermail/https-everywhere/attachments/20130210/9f167310/attachment.html>