more clearly mark the original post as historic

diff --git a/personal/_posts/2018-08-07-stacked-borrows.md b/personal/_posts/2018-08-07-stacked-borrows.md
index 0f36e05d5f9fe6a537ebebac4078204236fc1fd9..7397780b0edb87210813671bc800b0ebc3d54be6 100644 (file)
--- a/personal/_posts/2018-08-07-stacked-borrows.md
+++ b/personal/_posts/2018-08-07-stacked-borrows.md
@@ -18,6 +18,7 @@ But before I delve into my latest proposal, I want to briefly discuss a key diff
 **Update:**
 Since publishing this post, I have written [another]({% post_url 2018-11-16-stacked-borrows-implementation %}) blog post about a slightly adjusted version of Stacked Borrows (the first version that actually got implemented).
 That other post is self-contained, so if you are just interested in the current state of Stacked Borrows, I suggest you go there.
 **Update:**
 Since publishing this post, I have written [another]({% post_url 2018-11-16-stacked-borrows-implementation %}) blog post about a slightly adjusted version of Stacked Borrows (the first version that actually got implemented).
 That other post is self-contained, so if you are just interested in the current state of Stacked Borrows, I suggest you go there.

+Only go on reading here if you want some additional historic context.

 **/Update**
 
 ## 1 Validity-based vs. Access-based
 **/Update**
 
 ## 1 Validity-based vs. Access-based