Dan Nicholson

I'm still not totally sure what the best approach here is, but I think the fundamental change from replacing `loader` to exchanging `loader` is likely to have subtle effects that...

> > Since the replacing process needs to be supported in case `RENAME_EXCHANGE` is not available > > @dbnicholson FYI, I worked on a patch series to add `RENAME_EXCHANGE` support...

Pushing things out of order will definitely cause problems, but if you only have controlled clients it might be fine. Look at the ordering in the releng script and try...

@btkostner ostree does a lot of stats of the object tree, so it might be worth trying goofys without catfs. That way you get the metadata caching without the content...

I'm personally not opposed to making an abstraction layer between an OSTree repo and the underlying storage, but I think it's going to be an uphill battle. The way an...

> I don't really understand the local ref map. Is this only about the flatpak xa.cache issue, or do you actually expect ostree to use this? If so, how? >...

Given that the last commit does not have good agreement, I'll break that out into a separate PR and leave this just for the new API to handle updating the...

I rebased this on master now and dropped the "ref-map in ostree-metadata" commit. But I did add on an additional change I originally did in #490 to make the summary...

Oops, misread that and thought you were talking about deltas. That does seem like an excessive amount of memory. Possibly the object tracking is inefficient, or possibly it's leaking. I'm...

It's been a bit since I looked at the prune code, but this doesn't really seem like a leak. The prune code works by creating 2 hash tables storing the...