Skip to content
Snippets Groups Projects
  1. May 06, 2012
  2. May 08, 2012
    • Adrian Buehlmann's avatar
      parsers: statically initializing tp_new to PyType_GenericNew is not portable · 48e42f98
      Adrian Buehlmann authored
      As detailed on http://docs.python.org/extending/newtypes.html (quote):
      
        "In this case, we can just use the default implementation provided by the API
        function PyType_GenericNew(). We’d like to just assign this to the
        tp_new slot, but we can’t, for portability sake. On some platforms or
        compilers, we can’t statically initialize a structure member with a function
        defined in another C module, so, instead, we’ll assign the tp_new slot in the
        module initialization function just before calling PyType_Ready()."
      
      Fixes "gcc (GCC) 3.4.5 (mingw-vista special r3)" complaining with:
      
        mercurial/parsers.c:1096: error: initializer element is not constant
        mercurial/parsers.c:1096: error: (near initialization for `indexType.tp_new')
      48e42f98
  3. May 07, 2012
    • Patrick Mézard's avatar
      pure/base85: align exception type/msg on base85.c · 20a9d823
      Patrick Mézard authored
      brendan mentioned on IRC that b64decode raises a TypeError too, but while the
      previous exception type may be better in general, it is much easier to make it
      behave like the related C code and changes nothing for mercurial itself.
      20a9d823
    • Matt Mackall's avatar
      parsers: fix refcount bug on corrupt index · b767382a
      Matt Mackall authored
      When we encounter a corrupt index, we "fail" the init but our
      destructor still gets called. On some systems, this was causing us to
      attempt to decref a dangling to self->data.
      b767382a
  4. May 04, 2012
  5. May 03, 2012
  6. May 06, 2012
  7. May 04, 2012
  8. May 03, 2012
  9. May 02, 2012
  10. May 03, 2012
  11. May 02, 2012
  12. May 01, 2012
  13. Apr 30, 2012
  14. Apr 29, 2012
  15. Apr 30, 2012
    • Patrick Mézard's avatar
      4955e7bf
    • Patrick Mézard's avatar
      subrepo/svn: fix checked out rev number retrieval (issue2968) · ae2664ee
      Patrick Mézard authored
      The initial version was to take the "Revision" field from svn info. It works
      but produces false positive when parent paths are being moved or unrelated
      changes are being committed, causing it to change while the svn checkout itself
      remains the same. To avoid spurious commit, we took "Revision" and "Last
      Changed Rev" for general comparison and kept the latter to answer "what is your
      revision?" question. This is better but fails when the subrepo path exists at
      "Revision" but not at "Last Changed Rev". This patch adds a check for this, and
      returns "Revision" if the path does not exist. We try to avoid doing this as
      much as possible at it implies an extra, *remote* call.
      ae2664ee
    • Patrick Mézard's avatar
      amend: fix copy records handling (issue3410) · 9224cc2e
      Patrick Mézard authored
      Messing with the dirstate before the intermediate commit seems error prone.
      Instead, commit and recompute the copies with copies.pathcopies(), then use
      that with commitctx().
      
      Since copies.pathcopies() does not support file replacement very well, the
      whole .renamed() condition in samefile() is removed and the "file replacement
      caused by differing copy source" effect is discarded.
      
      Test shamelessly stolen from Idan Kamara <idankk86@gmail.com>
      9224cc2e
    • Patrick Mézard's avatar
      test-commit-amend: exhibit an --amend weirdness · 90ca344a
      Patrick Mézard authored
      The weirdness is --amend let you replace one file with another with same data
      and flags if the new file copy record differ from the one in the parent
      revision. In theory, there is no problem with this kind of thing, subversion
      supports it, but here we see log and status disagree. The reason is log reads
      the copy record from the filelog, while status calls copies.pathcopies() which
      eventually invokes some expensiveness argument to discard this case (copies.py,
      _forwardcopies(), line 132). Since the next patch will side with pathcopies(),
      I prefer to call this behaviour a bug.
      90ca344a
  16. Apr 29, 2012
  17. Apr 30, 2012
  18. Apr 28, 2012
Loading