Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | config test: clean up memory leak | Edward Thomson | 2014-10-26 | 1 | -0/+1 |
| | |||||
* | Change the length of the file so that the change is picked up. | Alan Rogers | 2014-10-23 | 1 | -2/+2 |
| | |||||
* | Add a test to make sure a new snapshot has the new value. | Alan Rogers | 2014-10-23 | 1 | -1/+14 |
| | |||||
* | config: refresh before reading a value | Carlos Martín Nieto | 2014-04-18 | 1 | -5/+0 |
| | | | | | | | | | | With the isolation of complex reads, we can now try to refresh the on-disk file before reading a value from it. This changes the semantics a bit, as before we could be sure that a string we got from the configuration was valid until we wrote or refreshed. This is no longer the case, as a read can also invalidate the pointer. | ||||
* | config: implement config snapshotting | Carlos Martín Nieto | 2014-04-18 | 1 | -0/+69 |
In order to have consistent views of the config files for remotes, submodules et al. and a configuration that represents what is currently stored on-disk, we need a way to provide a view of the configuration that does not change. The goal here is to provide the snapshotting part by creating a read-only copy of the state of the configuration at a particular point in time, which does not change when a repository's main config changes. |