Skip to content
Snippets Groups Projects
  1. Sep 22, 2016
  2. Sep 21, 2016
  3. Sep 20, 2016
  4. Sep 02, 2016
  5. Sep 20, 2016
    • Durham Goode's avatar
      manifest: add manifestlog.add · 6b5a9a01
      Durham Goode authored
      This adds a simple add() function to manifestlog. This lets us convert more
      uses of repo.manifest to use repo.manifestlog, so we can further break our
      dependency on the manifest class.
      6b5a9a01
    • Durham Goode's avatar
      manifest: move manifest.add onto manifestrevlog · 774a15b1
      Durham Goode authored
      This moves add and _addtree onto manifestrevlog. manifestrevlog is responsible
      for all serialization decisions, so therefore the add function should live on
      it. This will allow us to call add() from manifestlog, which lets us further
      break our dependency on manifest.
      774a15b1
    • Durham Goode's avatar
      manifest: remove dependency on treeinmem from manifest.add · da75bc36
      Durham Goode authored
      Currently manifest.add uses the treeinmem option to know if it can call
      fastdelta on the given manifest instance. In a future patch we will be moving
      add() to be on the manifestrevlog, so it won't have access to the treeinmem
      option anymore. Instead, let's have it actually check if the given manifest
      instance supports the fastdelta operation.
      
      This also means that if treemanifest or any implementation eventually implements
      fastdelta(), it will automatically benefit from this code path.
      da75bc36
    • Durham Goode's avatar
      manifest: move treeinmem onto manifestlog · 483003c2
      Durham Goode authored
      A previous patched moved all the serialization related options onto
      manifestrevlog (since it is responsible for serialization). Let's move the
      treeinmem option on manifestlog, since it is responsible for materialization
      decisions. This reduces the number of dependencies manifestlog has on the old
      manifest type as well, so we can eventually make them completely independent of
      each other.
      483003c2
  6. Sep 19, 2016
  7. Sep 20, 2016
  8. May 03, 2016
  9. Sep 19, 2016
    • Martin von Zweigbergk's avatar
      strip: don't use "full" and "partial" to describe bundles · 769aee32
      Martin von Zweigbergk authored
      The partial bundle is not a subset of the full bundle, and the full
      bundle is not full in any way that i see. The most obvious
      interpretation of "full" I can think of is that it has all commits
      back to the null revision, but that is not what the "full" bundle
      is. The "full" bundle is simply a backup of what the user asked us to
      strip (unless --no-backup). The "partial" bundle contains the
      revisions we temporarily stripped because they had higher revision
      numbers that some commit that the user asked us to strip.
      
      The "full" bundle is already called "backup" in the code, so let's use
      that in user-facing messages too. Let's call the "partial" bundle
      "temporary" in the code.
      769aee32
    • Martin von Zweigbergk's avatar
      strip: clarify that user action is required to recover temp bundle · 94ebf56d
      Martin von Zweigbergk authored
      If strip fails when applying the temporary bundle, the commits in the
      temporary bundle have not yet been applied, so the user will almost
      definitely want to apply the bundle. We should be more clear to the
      user about that than our current "partial bundle stored in...".
      
      Note that we will probably not be able to recover it automatically,
      since whatever made it fail (e.g. a hook) will most likely make it
      fail again. We need to give control back to the user to fix the
      problem before trying again.
      94ebf56d
  10. Sep 15, 2016
    • Martin von Zweigbergk's avatar
      strip: report both bundle files in case of exception (issue5368) · 44ef2162
      Martin von Zweigbergk authored
      If strip fails while recovering the temporary bundle (e.g. because a
      hook fails), we tell the user only about the backup bundle, not about
      the temporary bundle. Since the user did not ask to strip the commits
      in the temporary bundle, that's the more important bundle to mention,
      so let's do that (and also mention the backup bundle as usual).
      44ef2162
Loading