----- Original Message ----- > From: "Stefan Hajnoczi" <stefa...@redhat.com> > To: "Paolo Bonzini" <pbonz...@redhat.com> > Cc: qemu-devel@nongnu.org, "Stefan Hajnoczi" <stefa...@gmail.com>, "Thomas > Huth" <th...@redhat.com> > Sent: Thursday, February 16, 2017 11:20:42 AM > Subject: Re: [PATCH qemu-web] Add Andrea's virtual memory FOSDEM presentation > to blog post > > On Wed, Feb 15, 2017 at 04:00:44PM +0100, Paolo Bonzini wrote: > > On 15/02/2017 15:42, Stefan Hajnoczi wrote: > > > From: Stefan Hajnoczi <stefa...@gmail.com> > > > > > > Andrea's presentation touches on Transparent Huge Pages and post-copy > > > live migration using userfaultfd for virtualization use cases. > > > > > > Cc: Thomas Huth <th...@redhat.com> > > > Signed-off-by: Stefan Hajnoczi <stefa...@gmail.com> > > > --- > > > I don't know jekyll or how the blog is set up. Perhaps timestamps need > > > to be updated in the post file. Please fix up when applying. > > > > Right, I only had to add > > > > last_modified_at: 2017-02-15 15:49:00 +0100 > > > > to the header. So this will be also a nice example of how to update a > > post after the fact! > > Thanks for looking into it. > > Weird that the blog engine relies on manual metadata rather than using > file timestamps.
I think the reason is that the file timestamps can change for unrelated reasons: adding a new permalink or fixing a typo may not be worth of adding the "updated Feb 16, 2017" note on the page. Wordpress and the like probably have a similar behavior, you just don't see it because it's hidden in a database rather than part of a text file. :) Paolo
