[HTTPS-Everywhere] Where to reenable rules?

[Alexander Buchner]

On 09.04.2015 22:12, Jacob Hoffman-Andrews wrote:
> There's a short tutorial under
> https://www.eff.org/https-everywhere/development, starting about the
> middle of the page.
> 
> In short, you'll want to create a separate branch for each change,
> push the branch to your own fork, and create a pull request for that
> branch.

Thanks!

Right now my local master contains some commits which you can see in
https://github.com/EFForg/https-everywhere/pull/1333.

Should I try to revert them and create single pull requests for every
commit?

Creating a new branch off my master will right now also result in a
'big' pull request because my master already contains the before
mentioned commits.

At least, I think, now I get why I should create a new branch off master
for every commit.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: OpenPGP digital signature
URL: <https://lists.eff.org/pipermail/https-everywhere/attachments/20150409/0da40f5a/attachment.sig>