content: rename articles to reinforce convention of short URLs

The Go blog started out on Blogger
(http://web.archive.org/web/20100325005843/http://blog.golang.org/).
Later, we moved to the current self-hosted blog server
with extra Go-specific functionality like playground snippets.

The old Blogger posts have very long URLs that Blogger chose
for us, such as "go-programming-language-turns-two" or
"two-go-talks-lexical-scanning-in-go-and", predating
the convention of giving posts shorter, more share-friendly,
typeable names.

The conversion of the old Blogger posts also predated
the convention of putting supporting files in a subdirectory.

The result is that although we've established new conventions,
you wouldn't know by listing the directory - the old Blogger
content presents a conflicting picture.

This commit renames the posts with very long names
to have shorter, more share-friendly names, and it moves
all supporting files to subdirectories. It also adds a README
documenting the conventions.

For example, blog.golang.org/go-programming-language-turns-two
is now blog.golang.org/2years, matching our more recent birthday
post URLs, and its supporting files are moved to the new 2years/ directory.

The old URLs redirect to the new ones.

Change-Id: I9f46a790c2c8fab8459aeda73d4e3d2efc86d88f
Reviewed-on: https://go-review.googlesource.com/c/blog/+/223599
Run-TryBot: Russ Cox <rsc@golang.org>
Reviewed-by: Andrew Bonventre <andybons@golang.org>

1 files changed, 20 insertions, 0 deletions

diff --git a/content/debug-gdb.article b/content/debug-gdb.article
new file mode 100644
index 0000000..ff24c4f
--- /dev/null
+++ b/content/debug-gdb.article
@@ -0,0 +1,20 @@
+# Debugging Go programs with the GNU Debugger
+30 Oct 2011
+Tags: debug, gdb, technical
+Summary: Announcing a new article about debugging Go programs with GDB.
+OldURL: /debugging-go-programs-with-gnu-debugger
+
+Andrew Gerrand
+
+##
+
+Last year we [reported](https://blog.golang.org/2010/11/debugging-go-code-status-report.html)
+that Go's [gc](https://golang.org/cmd/gc/)/[ld](https://golang.org/cmd/6l/)
+toolchain produces DWARFv3 debugging information that can be read by the GNU Debugger (GDB).
+Since then, work has continued steadily on improving support for debugging Go code with GDB.
+Among the improvements are the ability to inspect goroutines and to print
+native Go data types,
+including structs, slices, strings, maps,
+interfaces, and channels.
+
+To learn more about Go and GDB, see the [Debugging with GDB](https://golang.org/doc/debugging_with_gdb.html) article.