X-Git-Url: http://git.nikiroo.be/?p=gofetch.git;a=blobdiff_plain;f=test%2Fexpected%2FLWN%2F0000763729.header;fp=test%2Fexpected%2FLWN%2F0000763729.header;h=be98c7cff2870b56ebf08cfc6fbaf687b06197fb;hp=934f640905ee2b9c17d916fe7349929fe057144d;hb=e818d449fee8a5397ab2f05df63bbeffc4c67dc0;hpb=a6a7ff9f2e7f42f17eaa69be2bfad201195b3eb4

diff --git a/test/expected/LWN/0000763729.header b/test/expected/LWN/0000763729.header
index 934f640..be98c7c 100644
--- a/test/expected/LWN/0000763729.header
+++ b/test/expected/LWN/0000763729.header
@@ -8,6 +8,12 @@ i    an  attacker; it's worse if it remains compromised even after a
 i    reboot.  Numerous  mechanisms  for  ensuring  the  integrity of
 i    installed  system files have been proposed and implemented over
 i    the  years.  But it seems there is always room for one more; to
-i    fill  that  space, the fs-verity mechanism is being proposed as
-i    a way to protect individual files from malicious modification.
+i    fill  that  space, the [1]fs-verity mechanism is being proposed
+i    as   a   way   to   protect  individual  files  from  malicious
+i    modification.
+i    
+i    
+i    
+i    [1] https://lwn.net/ml/linux-fsdevel/20180824161642.1144-1-ebi-
+i    ggers@kernel.org/
 i