Jonathan Lebon

Hmm, a similar idea I've had was to copy the features of `checkout --union/--union-add/--union-identical` to `commit`. Then you could do e.g. ``` ostree commit --union --tree=ref=rootfs --tree=dir=overlay-rootfs ```

Hmm OK, one thing I missed at first is that `--tree=prefix` affects every `--tree` afterwards, not just the next one, until the next `--tree=prefix`. Which is fine I suppose, though...

bot, retest this please

Looks like RPM build errors: ``` error: File not found: /srv/code/tests/installed/build/.build/ostree-2018.5.51.g5d1bf343-1.fc28.x86_64/usr/libexec/libostree/ostree-trivial-httpd RPM build errors: bogus date in %changelog: Sat Aug 25 2013 Colin Walters - 2013.5-3 bogus date in %changelog:...

Hmm, any reason we don't create a ref in the repo? I think this has come up before too.

I encountered https://gitlab.gnome.org/GNOME/libglnx/-/merge_requests/41 while hacking on this, which took me some time to figure out!

> Today, the ostree-ext container logic discards everything not in `/usr` (or `/etc`). But, we could choose to make it as easy to do this as: Sure, I think this...

>> The UX described in the demo above is quite streamlined in comparison. > > I find this a bit more debatable :smile: Heh fair. The `mkdir` is definitely nicer....

Ahh that's a tricky corner case. It's not at all obvious that doing a commit-only pull only would negatively affect static deltas. I guess a reflog would have been useful...

> You could run it under valgrind or similar to see if anything comes up. Yeah, was playing with that yesterday on a (much smaller) local repo. Valgrind found no...