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/pipelines.article | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'content/pipelines.article') diff --git a/content/pipelines.article b/content/pipelines.article index f2fe186..c898135 100644 --- a/content/pipelines.article +++ b/content/pipelines.article @@ -1,7 +1,7 @@ # Go Concurrency Patterns: Pipelines and cancellation 13 Mar 2014 Tags: concurrency, pipelines, cancellation -Summary: Go's concurrency primitives make it easy to construct streaming data pipelines that make efficient use of I/O and multiple CPUs. This article presents examples of such pipelines, highlights subtleties that arise when operations fail, and introduces techniques for dealing with failures cleanly. +Summary: How to use Go's concurrency to build data-processing pipelines. Sameer Ajmani -- cgit v1.2.3