Next | Query returned 37 messages, browsing 31 to 40 | previous

History of commit frequency

CVS Commit History:


   2018-03-04 16:52:21 by Benny Siegert | Files touched by this commit (95) | Package updated
Log message:
Revbump all Go packages after Go 1.10 update.
   2017-04-13 17:12:07 by Benny Siegert | Files touched by this commit (39) | Package updated
Log message:
Revbump all Go packages after the Go 1.8.1 update.
   2016-12-04 17:30:01 by Benny Siegert | Files touched by this commit (35) | Package updated
Log message:
Revbump Go packages after 1.7.4 update.
   2016-10-29 10:59:49 by Benny Siegert | Files touched by this commit (34) | Package updated
Log message:
Revbump packages depending on Go after the Go 1.7.3 update.
   2016-09-10 21:47:21 by Benny Siegert | Files touched by this commit (30) | Package updated
Log message:
Revbump all Go packages after the Go 1.7.1 update.
   2016-08-28 13:47:48 by Thomas Klausner | Files touched by this commit (1)
Log message:
Set GITHUB_PROJECT to fix fetch phase.
   2016-08-21 11:14:25 by Benny Siegert | Files touched by this commit (5)
Log message:
New package, go-gls-4.2.0.

Every so often, a thread shows up on the golang-nuts asking for some form of
goroutine-local-storage, or some kind of goroutine id, or some kind of context.
There are a few valid use cases for goroutine-local-storage, one of the most
prominent being log line context. One poster was interested in being able to
log an HTTP request context id in every log line in the same goroutine as the
incoming HTTP request, without having to change every library and function call
he was interested in logging.

It is my duty to point you to https://blog.golang.org/context, which is how
Google solves all of the problems you'd perhaps consider using this package for
at scale.

Next | Query returned 37 messages, browsing 31 to 40 | previous