From faf1e2da2d911edc717993e8edb24fe88f99b2b5 Mon Sep 17 00:00:00 2001 From: Russ Cox Date: Sat, 14 Mar 2020 09:44:01 -0400 Subject: content: write real summary for each article The pre-Markdown blog invented a summary by copying the first paragraph of text. Often this was nonsense or at least useless. The new Markdown-enabled present format adds an explicit Summary line. The conversion populated these with the same first paragraph that the old format would have used implicitly. This commit rewrites them all to be proper short summaries. Change-Id: If2e1e101b95558d7ecd53c613f733a7f89c680f1 Reviewed-on: https://go-review.googlesource.com/c/blog/+/223598 Run-TryBot: Russ Cox Reviewed-by: Andrew Bonventre --- content/share-memory-by-communicating.article | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'content/share-memory-by-communicating.article') diff --git a/content/share-memory-by-communicating.article b/content/share-memory-by-communicating.article index 12bff79..c254ea0 100644 --- a/content/share-memory-by-communicating.article +++ b/content/share-memory-by-communicating.article @@ -1,7 +1,7 @@ # Share Memory By Communicating 13 Jul 2010 Tags: concurrency, technical -Summary: Traditional threading models (commonly used when writing Java, C++, and Python programs, for example) require the programmer to communicate between threads using shared memory. Typically, shared data structures are protected by locks, and threads will contend over those locks to access the data. In some cases, this is made easier by the use of thread-safe data structures such as Python's Queue. +Summary: A preview of the new Go codelab, Share Memory by Communicating. Andrew Gerrand -- cgit v1.2.3