Skip to content
Snippets Groups Projects
  1. Sep 24, 2013
  2. Sep 20, 2013
  3. Sep 19, 2013
    • durin42's avatar
      sslutil: add a config knob to support TLS (default) or SSLv23 (bc) (issue4038) · 47ff9d1abfa9
      durin42 authored
      Prior to this change, we default to SSLv23, which is insecure because
      it allows use of SSLv2. Unfortunately, there's no constant for OpenSSL
      to let us use SSLv3 or TLS - we have to pick one or the other. We
      expose a knob to revert to pre-TLS SSL for the user that has an
      ancient server that lacks proper TLS support.
      47ff9d1abfa9
  4. Sep 24, 2013
  5. Sep 06, 2013
  6. Jul 24, 2013
  7. Sep 23, 2013
  8. Sep 20, 2013
  9. Sep 23, 2013
  10. Sep 22, 2013
  11. Sep 19, 2013
  12. Sep 22, 2013
  13. Sep 06, 2013
  14. Sep 21, 2013
    • Katsunori FUJIWARA's avatar
      largefiles: setup "largefiles" feature in each repositories individually · fb6e87d93948
      Katsunori FUJIWARA authored
      Before this patch, if largefiles extension is enabled once in any of
      target repositories, commands handling multiple repositories at a time
      like below misunderstand that "largefiles" feature is supported also
      in all other local repositories:
      
        - clone/pull from or push to localhost
        - recursive execution in subrepo tree
      
      This patch registers "featuresetup()" into "featuresetupfuncs" of
      "localrepository" to support "largefiles" features only in
      repositories enabling largefiles extension, instead of adding
      "largefiles" feature to class variable "_basesupported" of
      "localrepository".
      
      This patch also adds checking below to the largefiles specific class
      derived from "localrepository":
      
        - push to localhost: whether features supported in the local(= dst)
          repository satisfies ones required in the remote(= src)
      
      This can prevent useless looking up in the remote repository, when
      supported and required features are mismatched: "push()" of
      "localrepository" also checks it, but it is executed after looking up
      in the remote.
      fb6e87d93948
    • Katsunori FUJIWARA's avatar
      localrepo: make supported features manageable in each repositories individually · 55ef79031009
      Katsunori FUJIWARA authored
      Before this patch, all localrepositories support same features,
      because supported features are managed by the class variable
      "supported" of "localrepository".
      
      For example, "largefiles" feature provided by largefiles extension is
      recognized as supported, by adding the feature name to "supported" of
      "localrepository".
      
      So, commands handling multiple repositories at a time like below
      misunderstand that such features are supported also in repositories
      not enabling corresponded extensions:
      
        - clone/pull from or push to localhost
        - recursive execution in subrepo tree
      
      "reposetup()" can't be used to fix this problem, because it is invoked
      after checking whether supported features satisfy ones required in the
      target repository.
      
      So, this patch adds the set object named as "featuresetupfuncs" to
      "localrepository" to manage hook functions to setup supported features
      of each repositories.
      
      If any functions are added to "featuresetupfuncs", they are invoked,
      and information about supported features is managed in each
      repositories individually.
      
      This patch also adds checking below:
      
        - pull from localhost: whether features supported in the local(= dst)
          repository satisfies ones required in the remote(= src)
      
        - push to localhost: whether features supported in the remote(= dst)
          repository satisfies ones required in the local(= src)
      
      Managing supported features by the class variable means that there is
      no difference of supported features between each instances of
      "localrepository" in the same Python process, so such checking is not
      needed before this patch.
      
      Even with this patch, if intermediate bundlefile is used as pulling
      source, pulling indirectly from the remote repository, which requires
      features more than ones supported in the local, can't be prevented,
      because bundlefile has no information about "required features" in it.
      55ef79031009
    • Katsunori FUJIWARA's avatar
      extensions: list up only enabled extensions, if "ui" is specified · 6f72e7d28b35
      Katsunori FUJIWARA authored
      Before this patch, "extensions.extensions()" always lists up all
      loaded extensions. So, commands handling multiple repositories at a
      time like below enable extensions unexpectedly.
      
        - clone from or push to localhost: extensions enabled only in the
          source are enabled also in the destination
      
        - pull from localhost: extensions enabled only in the destination
          are enabled also in the source
      
        - recursive execution in subrepo tree: extensions enabled only in
          the parent or some of siblings in the tree are enabled also in
          others
      
      In addition to it, extensions disabled locally may be enabled
      unexpectedly.
      
      This patch checks whether each of extensions should be listed up or
      not, if "ui" is specified to "extensions.extensions()", and invokes
      "reposetup()" of each extensions only for repositories enabling it.
      6f72e7d28b35
  15. Sep 23, 2013
  16. Sep 20, 2013
  17. Jul 14, 2013
Loading