-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 12/04/2013 11:16 AM, Daniel Kahn Gillmor wrote: > On 12/04/2013 01:10 PM, Yan wrote: >> Peter was going to do this because I don't yet have push access >> to the Git repository. Peter, the tag should be in my remote. > > Yan, can you point the rest of the list toward your remote in the > meantime? Peter already fixed the official repo: https://gitweb.torproject.org/https-everywhere.git For reference, mine is at https://github.com/diracdeltas/https-everywhere/, and Peter's is https://github.com/pde/https-everywhere/. In theory, the 'master' and '3.0' branches on both will be kept up-to-date with the official one on torproject.org. We use Github mostly because some contributors prefer to fork and open pull requests, rather than emailing patches. It also has some significant UI improvements over Gitweb and Trac. Having said that, we will continue to respect the concerns that you mentioned in this email a while back: https://lists.eff.org/pipermail/https-everywhere/2013-August/001776.html In summary, here are the current options for getting contributions into HTTPS Everywhere: * Email a patch to [email protected] (for rulesets) or [email protected] (for other). Alternatively, point us to a remote where the changes live. * Open a pull request at either Peter's or my repository. They should be equivalent in terms of efficiency once I have push access to the official one. * Attach a patch to a ticket at https://trac.torproject.org/projects/tor/report/19. This is probably slower than the other methods. :) > > Also, while y'all are updating this stuff, the available HTTPS-E > version numbers in the trac instance at > https://trac.torproject.org/projects/tor/newticket don't contain > 3.4.3 > It doesn't contain 3.4.2 either. Thanks for bringing that to our attention. - -Yan > thanks, > > --dkg > > > > _______________________________________________ HTTPS-Everywhere > mailing list [email protected] > https://lists.eff.org/mailman/listinfo/https-everywhere > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJSn4kkAAoJENC7YDZD/dnsftAH+wVw+72KnI++IzwmUtleBH2k 4mbFvXxp6BxJMcP0EMTO3CVxyNrYVMR0d7rtSr6asfUwZUhnR2u5Sq1/CH4olbOz 87N4oQxolfxbpF0RSrjJTYDLUR9lzZo81JMiitAvY+PGBKDixA8DLge+YbNDnmc8 lxf6X0LW2clu/yxbfW61kc9sAzL18N+AWm+YLpD+ZNaeqiDFEfZvX6xQYqaHcSSt CjfeEGVyRFbXPIW84KNMbrsBDpbsjBH6+qRayWxYZvFVeFPub7SFPB+hS4ce563u /zplpfEzV7zGgcBK1VMznNmtD6azdvKx5njBhPO8OqfPXhjbx0nRaEled9OMVBs= =/Yrw -----END PGP SIGNATURE----- _______________________________________________ HTTPS-Everywhere mailing list [email protected] https://lists.eff.org/mailman/listinfo/https-everywhere
