Skip to content
Snippets Groups Projects
  1. Jul 02, 2014
  2. Jun 30, 2014
  3. Jun 07, 2014
  4. Jun 29, 2014
    • Angel Ezquerra's avatar
      repoview: do not crash when localtags refers to non existing revisions · 925d1bb9a971
      Angel Ezquerra authored
      This fixes a crash that may happen when using mercurial 3.0.x.
      
      The _gethiddenblockers function assumed that the output of tags.readlocaltags()
      was a dict mapping tags to of valid nodes. However this was not necessarily the
      case. When a repository had obsolete revisions and had local tag pointing to a
      non existing revision was found, many mercurial commands would crash.
      
      This revision fixes the problem by removing any tags from the output of
      tags.readlocaltags() which point to invalid nodes.
      
      We may want to add a warning when this happens (although it might be
      annoying to get that warning for every command, possibly even more than once per
      command).
      
      A test for this problem has been added to test-obsolete.t. Without this fix the
      test would output:
      
        $ hg tags
        abort: 00changelog.i@3816541e5485: no node!
        [255]
      
      Instead of:
      
        $ hg tags
        tiptag                             2:3816541e5485
        tip                                2:3816541e5485
        visible                            0:193e9254ce7e
      925d1bb9a971
  5. Jun 25, 2014
    • Siddharth Agarwal's avatar
      match: make glob '**/' match the empty string · a4b67bf1f0a5
      Siddharth Agarwal authored
      Previously, a glob pattern of the form 'foo/**/bar' would match 'foo/a/bar' but
      not 'foo/bar'. That was because the '**' in 'foo/**/bar' would be translated to
      '.*', making the final regex pattern 'foo/.*/bar'. That pattern doesn't match
      the string 'foo/bar'.
      
      This is a bug because the '**/' glob matches the empty string in standard Unix
      shells like bash and zsh.
      
      Fix that by making the ending '/' optional if an empty string can be matched.
      a4b67bf1f0a5
  6. Jun 19, 2014
  7. Jun 18, 2014
  8. Jun 16, 2014
  9. Jun 14, 2014
  10. Jun 13, 2014
  11. Jun 09, 2014
  12. Jun 11, 2014
  13. May 26, 2014
    • Mads Kiilerich <madski at unity3d.com>'s avatar
      resolve: keep wlock while resolving · 14560418856d
      Mads Kiilerich authored
      This will make resolve use correct locking and thus make it more safe.
      
      Resolve is usually a long running command spending a lot of time waiting for
      user input on hard problems. It is thus a real world scenario to start multiple
      resolves at once or run other commands (such as up -C and merge) while resolve
      is running. Proper locking prevents that.
      14560418856d
  14. Jun 05, 2014
    • Katsunori FUJIWARA's avatar
      keyword: suppress keyword expansion while 'hg fetch' for internal merge · 2668a78df8ba
      Katsunori FUJIWARA authored
      Before this patch, 'hg fetch' may cause unexpected conflict, if 'hg
      fetch'-ed changes are located near lines in which keywords are
      embedded, because keywords are substituted with other strings in the
      working directory.
      
      This patch suppresses keyword expansion while 'hg fetch' for internal
      merge by adding 'fetch' to 'restricted' command list like 'merge'.
      
      This patch uses 'hg import' to safely create the new head to be merged
      at succeeding 'hg fetch', because:
      
        - branch of revision #10 is different from one of #11 in 'Test'
          repository, so just 'hg fetch -r 11' doesn't cause merging between
          them
      
          this means the new head should be created manually.
      
        - 'hg import' is easier and safer than 'cat <<EOF' and 'hg commit'
          to replay same changes including special characters like '$'
      
          safeness of 'hg import' with keyword extension is already examined
          in 'test-keyword.t'.
      2668a78df8ba
    • Katsunori FUJIWARA's avatar
      keyword: suppress keyword expansion while 'hg histedit' for internal merge · e22cfd1ae97c
      Katsunori FUJIWARA authored
      Before this patch, 'hg histedit' may cause unexpected conflict, if 'hg
      histedit'-ed changes are located near lines in which keywords are
      embedded, because keywords are substituted with other strings in the
      working directory.
      
      This patch suppresses keyword expansion while 'hg histedit' for
      internal merge by adding 'histedit' to 'restricted' command list like
      'merge'.
      
      Test in this patch just swaps order of revision #13 and #14: this is
      enough to cause internal merge.
      e22cfd1ae97c
    • Katsunori FUJIWARA's avatar
      keyword: suppress keyword expansion while 'hg backout' for internal merge · 5c64c338fa9f
      Katsunori FUJIWARA authored
      Before this patch, 'hg backout' may cause unexpected conflict, if 'hg
      backout'-ed changes are located near lines in which keywords are
      embedded, because keywords are substituted with other strings in the
      working directory.
      
      This patch suppresses keyword expansion while 'hg backout' for
      internal merge by adding 'backout' to 'restricted' command list like
      'merge'.
      5c64c338fa9f
    • Katsunori FUJIWARA's avatar
      keyword: suppress keyword expansion while 'hg graft' for internal merge · dd5ca1a32109
      Katsunori FUJIWARA authored
      Before this patch, 'hg graft' may cause unexpected conflict, if 'hg
      graft'-ed changes are located near lines in which keywords are
      embedded, because keywords are substituted with other strings in the
      working directory.
      
      This patch suppresses keyword expansion while 'hg graft' for internal
      merge by adding 'graft' to 'restricted' command list like 'merge'.
      dd5ca1a32109
    • Katsunori FUJIWARA's avatar
      keyword: suppress keyword expansion while 'hg rebase' for internal merge · 65dd65c645ed
      Katsunori FUJIWARA authored
      Before this patch, 'hg rebase' may cause unexpected conflict, if 'hg
      rebase'-ed changes are located near lines in which keywords are
      embedded, because keywords are substituted with other strings in the
      working directory.
      
      This patch suppresses keyword expansion while 'hg rebase' for internal
      merge by adding 'rebase' to 'restricted' command list like 'merge'.
      
      This patch specifies '--keep' to 'hg rebase', because revision #10 is
      useful also for tests in succeeding patches.
      65dd65c645ed
    • Katsunori FUJIWARA's avatar
      keyword: suppress keyword expansion while 'hg unshelve' for internal merge · 99f7e5fe35f2
      Katsunori FUJIWARA authored
      Before this patch, 'hg unshelve' may cause unexpected conflict, if 'hg
      unshelve'-ed changes are located near lines in which keywords are
      embedded, because keywords are substituted with other strings in the
      working directory.
      
      This patch suppresses keyword expansion while 'hg unshelve' for
      internal merge by adding 'unshelve' to 'restricted' command list like
      'merge'.
      99f7e5fe35f2
  15. Jun 01, 2014
  16. May 22, 2014
  17. May 30, 2014
  18. May 07, 2014
  19. May 22, 2014
    • Pierre-Yves David's avatar
      wireproto: expose the list of getbundle arguments to extensions · 3cb2da25b171
      Pierre-Yves David authored
      For now, getbundle accepts a fixed number of arguments: ``heads``, ``common``
      and ``bundlecaps``. We make this list exposed at the module level to let
      extensions add content there. This is important for extensions that wish to use
      bundle2 for other contents than changegroup.
      3cb2da25b171
  20. May 08, 2014
  21. May 17, 2014
  22. May 27, 2014
  23. May 17, 2014
    • Yuya Nishihara's avatar
      alias: handle shlex error in command aliases · c5afb07c33d3
      Yuya Nishihara authored
      No command should fail with ValueError just because there is unparseable
      alias definition.
      
      It returns 1 like other badalias handlers, but should be changed to 255 in
      a later version because we use 255 for general command error.
      c5afb07c33d3
Loading