Wed, 02 Jan 2019 05:07:03 +0100 strip: compute bookmark target only if we have bookmark to move
Boris Feld <boris.feld@octobus.net> [Wed, 02 Jan 2019 05:07:03 +0100] rev 41104
strip: compute bookmark target only if we have bookmark to move This is a small change that seems to make sense.
Wed, 02 Jan 2019 05:01:15 +0100 strip: extract code to create strip backup
Boris Feld <boris.feld@octobus.net> [Wed, 02 Jan 2019 05:01:15 +0100] rev 41103
strip: extract code to create strip backup We will reuse this for soft stripping.
Wed, 02 Jan 2019 04:57:47 +0100 strip: clarify comment around bundle create
Boris Feld <boris.feld@octobus.net> [Wed, 02 Jan 2019 04:57:47 +0100] rev 41102
strip: clarify comment around bundle create We may create two bundles, one for the changeset actually stripped, and one for the changeset affected by the strip we want to keep. (Changesets with a higher rev number than the striped ones). For soft stripping, we still need to the first one (used for "restoring" the changesets), but not the second one. We start with clarifying which bits of the code is used for what.
Wed, 02 Jan 2019 05:02:25 +0100 strip: move attributes shortcut assigned earlier
Boris Feld <boris.feld@octobus.net> [Wed, 02 Jan 2019 05:02:25 +0100] rev 41101
strip: move attributes shortcut assigned earlier This series will add support for "soft" stripping using the archived phase in addition to the usual heavy weight revlog stripping. First, we need to refactor the strip function to extract logic common to the "soft-strip" case. We are about to extract bits of the strip function into separate functions. Those blocks of code contain variables for frequently accessed attributes. We move those variables outside of the soon to be moved blocks.
Thu, 27 Dec 2018 17:16:40 +0530 log: fix line wrap on diffstat with -G/--graph (issue5800)
Navaneeth Suresh <navaneeths1998@gmail.com> [Thu, 27 Dec 2018 17:16:40 +0530] rev 41100
log: fix line wrap on diffstat with -G/--graph (issue5800) Differential Revision: https://phab.mercurial-scm.org/D5485
Wed, 02 Jan 2019 21:49:40 -0500 registrar: minor cleanup to the merge function
Matt Harbison <matt_harbison@yahoo.com> [Wed, 02 Jan 2019 21:49:40 -0500] rev 41099
registrar: minor cleanup to the merge function Pointed out by Yuya.
Wed, 02 Jan 2019 10:31:14 +0100 vfs: raise NotImplementedError in abstractvfs._auditvfs
Boris Feld <boris.feld@octobus.net> [Wed, 02 Jan 2019 10:31:14 +0100] rev 41098
vfs: raise NotImplementedError in abstractvfs._auditvfs This make sure that auditing is implemented.
Wed, 02 Jan 2019 10:29:36 +0100 vfs: handle _auditpath in proxyvfs
Boris Feld <boris.feld@octobus.net> [Wed, 02 Jan 2019 10:29:36 +0100] rev 41097
vfs: handle _auditpath in proxyvfs Just forward the call to the underlying vfs.
Wed, 02 Jan 2019 10:29:12 +0100 vfs: fix proxyvfs inheritance
Boris Feld <boris.feld@octobus.net> [Wed, 02 Jan 2019 10:29:12 +0100] rev 41096
vfs: fix proxyvfs inheritance The proxyvfs class is designed to overwrite some of the vfs logic. Yet, it did not use normal class inheritance. This is becoming an issue as `abstractvfs` method could take precedence over their `proxyvfs` version. We fix the inheritance chain to be as expected.
Wed, 26 Dec 2018 13:44:37 +0100 vfs: also audit rename
Boris Feld <boris.feld@octobus.net> [Wed, 26 Dec 2018 13:44:37 +0100] rev 41095
vfs: also audit rename Renaming through the vfs is not used in many places, and none of them seems to be a security risk. However, it is still worthwhile to run the auditing on rename file to perform developer-warning level checks.
(0) -30000 -10000 -3000 -1000 -300 -100 -10 +10 +100 +300 +1000 +3000 +10000 tip