From: Ralf Jung <post@ralfj.de>
Date: Wed, 1 May 2019 10:14:08 +0000 (+0200)
Subject: more clearly mark the original post as historic
X-Git-Url: https://git.ralfj.de/web.git/commitdiff_plain/32f4cd5d88a9e1ffcb88edd72ade73635ad79e71?hp=8b615c0e6fac065adcb407fb17a6b7f7e1ea6dd0

more clearly mark the original post as historic
---

diff --git a/ralf/_posts/2018-08-07-stacked-borrows.md b/ralf/_posts/2018-08-07-stacked-borrows.md
index 0f36e05..7397780 100644
--- a/ralf/_posts/2018-08-07-stacked-borrows.md
+++ b/ralf/_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.
+Only go on reading here if you want some additional historic context.
 **/Update**
 
 ## 1 Validity-based vs. Access-based