Next | Query returned 20 messages, browsing 11 to 20 | previous

History of commit frequency

CVS Commit History:


   2020-08-14 22:01:40 by Benny Siegert | Files touched by this commit (194) | Package updated
Log message:
Revbump all Go packages after go114 update
   2020-07-17 20:04:33 by Benny Siegert | Files touched by this commit (196) | Package updated
Log message:
Revbump all Go packages after go114 update.
   2020-06-17 11:54:20 by Benny Siegert | Files touched by this commit (188) | Package updated
Log message:
Revbump Go packages after Go 1.14.4 update.
   2020-04-28 13:46:30 by Nikita | Files touched by this commit (29)
Log message:
adjust maintainer to my new login
   2020-04-12 13:01:51 by Benny Siegert | Files touched by this commit (171)
Log message:
Revbump all Go packages after default version switch to 1.14.
   2020-03-21 17:57:21 by Benny Siegert | Files touched by this commit (170) | Package updated
Log message:
Revbump all Go packages after go113 update.
   2020-02-02 15:19:15 by Benny Siegert | Files touched by this commit (169) | Package updated
Log message:
Revbump all Go packages after go113 update.
   2020-01-10 14:32:32 by Benny Siegert | Files touched by this commit (169)
Log message:
Revbump Go packages after Go default version bump.
   2019-12-13 08:44:06 by Benny Siegert | Files touched by this commit (168) | Package updated
Log message:
Revbump all Go packages after Go 1.12.14 update.
   2019-11-06 14:35:18 by ng0 | Files touched by this commit (5)
Log message:
Add www/go-mux version 1.7.3

Go-mux implements a request router and dispatcher for matching
incoming requests to their respective handler.

The name mux stands for "HTTP request multiplexer". Like the standard
http.ServeMux, mux.Router matches incoming requests against a list of
registered routes and calls a handler for the route that matches the
URL or other conditions. The main features are:

It implements the http.Handler interface so it is compatible with the
standard http.ServeMux.
Requests can be matched based on URL host, path, path prefix, schemes,
header and query values, HTTP methods or using custom matchers.
URL hosts, paths and query values can have variables with an optional
regular expression.
Registered URLs can be built, or "reversed", which helps maintaining
references to resources.
Routes can be used as subrouters: nested routes are only tested if the
parent route matches. This is useful to define groups of routes that
share common conditions like a host, a path prefix or other repeated
attributes. As a bonus, this optimizes request matching.

Next | Query returned 20 messages, browsing 11 to 20 | previous