|
90aa2bf3
|
2014-10-25T19:51:12
|
|
config test: clean up memory leak
|
|
1e2fe921
|
2014-10-21T09:29:17
|
|
Change the length of the file so that the change is picked up.
|
|
|
5490c9d4
|
2014-10-16T13:52:55
|
|
Add a test to make sure a new snapshot has the new value.
|
|
523032cd
|
2014-03-31T09:58:44
|
|
config: refresh before reading a value
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.
|
|
|
55ebd7d3
|
2014-03-13T17:11:34
|
|
config: implement config snapshotting
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.
|