Merge branch 'wip/stacked-overlay'

diff --cc fusefile.8
index 194f4aa83558057c4c62d859dbab9a2219445940,da2b645b7825d2b7cad2a9999682ff37331708a4..b952f5574075e2ae9b0df699ead855873618a772
--- 1/fusefile.8
--- 2/fusefile.8
+++ b/fusefile.8
@@@ -33,11 -31,16 +33,16 @@@ any new written fused file regions foll
  distinguish between new, written content and old content that comes
  from the fragments.
  
+ By instead using the \fB-overlay:\fIlist\fR argument where \fIlist\fR
+ is a colon-separated list of filenames, \fBfusefile\fR will use those
+ as an ordered stack of overlays and "inject" them as fragments on top
+ of each other.
+ 
  The option \fB-dump\fR as first argument together with a fusefile
  setup will print the setup to standard output rather than establishing
 -a fusefile mount. This is of most use with a prior overlay setup,
 -where then the printout includes the portions of updates that have
 -been captured in the overlay. The printout is the series of fusefile
 +a fusefile mount. This is of most use with a prior overlay setup where
 +then the printout includes the portions of updates that have been
 +captured in the overlay. The printout is the series of fusefile
  fragment argments to give in order to intersperse the captured overlay
  portions according to the overlay table.
  

diff --cc fusefile.c
Simple merge