dirstate-scoping [22] remove various useless explicit backup
- Feb 23, 2023
-
-
Pierre-Yves David authored
The transaction file generation is already dealing with the backup for this. So, no need to duplicate such backup.
-
- Feb 22, 2023
-
-
Pierre-Yves David authored
The transaction file generation is already dealing with the backup for this. So, no need to duplicate such backup.
-
- Feb 23, 2023
-
-
Pierre-Yves David authored
-
Pierre-Yves David authored
It will be simpler if all write happens within transaction.
-
Pierre-Yves David authored
That way, the narrow spec changes will be done within a transaction.
-
Pierre-Yves David authored
It will be simpler if all write happens within transaction.
-
Pierre-Yves David authored
Now that the transaction manage the writes, we can simply use the transaction for backup. Some extra cleanup to ensure all changes happens within a transaction will be made in the next changesets.
-
Pierre-Yves David authored
This make it more transactional and will help us to simplify their backup. The implementation is not great, but it keep the patch simple as this is not the time for a larger refactoring yet.
-
Pierre-Yves David authored
This make it more transactional and will help us to simplify their backup. The implementation is not great, but it keep the patch simple as this is not the time for a larger refactoring yet.
-
Pierre-Yves David authored
Relying on disk data make the transactionally of this change complicated, so let us start reading data from other API instead.
-
- Feb 22, 2023
-
-
Pierre-Yves David authored
The tracking configuration we modify must be read under lock. So we grab the lock sooner.
-
- Feb 23, 2023
-
-
Pierre-Yves David authored
This will help us to improve the locking scope in the `tracked` command.
-