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

History of commit frequency

CVS Commit History:


   2017-06-05 16:25:36 by Ryo ONODERA | Files touched by this commit (2298)
Log message:
Recursive revbump from lang/perl5 5.26.0
   2016-06-08 21:25:20 by Thomas Klausner | Files touched by this commit (2236)
Log message:
Bump PKGREVISION for perl-5.24.
   2015-11-03 02:56:36 by Alistair G. Crooks | Files touched by this commit (368)
Log message:
Add SHA512 digests for distfiles for databases category

Problems found with existing distfiles:
	distfiles/D6.data.ros.gz
	distfiles/cstore0.2.tar.gz
	distfiles/data4.tar.gz
	distfiles/sphinx-2.2.7-release.tar.gz
No changes made to the cstore or mariadb55-client distinfo files.

Otherwise, existing SHA1 digests verified and found to be the same on
the machine holding the existing distfiles (morden).  All existing
SHA1 digests retained for now as an audit trail.
   2015-08-06 02:15:47 by Wen Heping | Files touched by this commit (2)
Log message:
Update to 0.001005

Upstream changes:
0.001005  2015-01-29 17:47:49-06:00 America/Chicago
 - Fix error message for missing values (Thanks Wes Malone!)
   2015-06-12 12:52:19 by Thomas Klausner | Files touched by this commit (3152)
Log message:
Recursive PKGREVISION bump for all packages mentioning 'perl',
having a PKGNAME of p5-*, or depending such a package,
for perl-5.22.0.
   2014-12-07 23:06:50 by Makoto Fujiwara | Files touched by this commit (2)
Log message:
Update 0.001003 to 0.001004
0.001004  2014-11-30 21:50:34-06:00 America/Chicago
 - Fix bug that disallowed false values
   2014-07-28 02:22:43 by Wen Heping | Files touched by this commit (3)
Log message:
Import DBIx-Introspector-0.001003 as databases/p5-DBIx-Introspector.

DBIx::Introspector is a module factored out of the DBIx::Class
database detection code. Most code that needs to detect which
database it is connected to assumes that there is a one-to-one
mapping from database drivers to database engines. Unfortunately
reality is rarely that simple. For instance, DBD::ODBC is typically
used to connect to SQL Server, but ODBC can be used to connect
to PostgreSQL, MySQL, and Oracle. Additionally, while ODBC is the
most common way to connect to SQL Server, it is not the only option,
as DBD::ADO can also be used.

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