Next | Query returned 21 messages, browsing 1 to 10 | Previous

History of commit frequency

CVS Commit History:


   2009-10-17 14:37:00 by Takahiro Kambe | Files touched by this commit (17) | Package removed
Log message:
Remove old ruby-DBI and ruby-DBD-* pacakges.
   2009-06-14 19:43:27 by Joerg Sonnenberger | Files touched by this commit (120)
Log message:
Remove @dirrm entries from PLISTs
   2008-10-16 23:43:54 by Eric Haszlakiewicz | Files touched by this commit (1)
Log message:
This package needs ruby-pg in order to work.
Also, note the possibility of changing RUBY_DBI_VERSION
   2008-06-22 17:45:12 by Takahiro Kambe | Files touched by this commit (2)
Log message:
Update ruby-DBI pacakge to 0.2.0, ruby-DBD-postgresql part.
   2008-06-19 16:44:06 by Takahiro Kambe | Files touched by this commit (6)
Log message:
Switch to use vendor_dir with Ruby 1.8.7.

Bump PKGREVISION.
   2008-03-13 18:38:49 by Joerg Sonnenberger | Files touched by this commit (29)
Log message:
Make PostgreSQL 8.2 the default version. Bump all packages using it.
Remove PostgreSQL 8.0 as choice.
   2007-03-17 16:53:45 by Takahiro Kambe | Files touched by this commit (1) | Package updated
Log message:
Reset PKGREVISION because of (implicitly) update ruby-DBD-postgresql
pacakge to 0.1.1
   2006-12-28 13:12:59 by Joerg Sonnenberger | Files touched by this commit (30)
Log message:
Change PostgreSQL default version to 8.1 and bump revision of all
packages which have it active by default.
   2006-08-17 15:07:45 by Takahiro Kambe | Files touched by this commit (3)
Log message:
Update ruby-DBD packages to 0.0.21, database denended parts.
Changes from 0.1.0 are huge, please refer ChangeLog.
   2006-03-04 22:31:14 by Johnny C. Lam | Files touched by this commit (2257)
Log message:
Point MAINTAINER to pkgsrc-users@NetBSD.org in the case where no
developer is officially maintaining the package.

The rationale for changing this from "tech-pkg" to \ 
"pkgsrc-users" is
that it implies that any user can try to maintain the package (by
submitting patches to the mailing list).  Since the folks most likely
to care about the package are the folks that want to use it or are
already using it, this would leverage the energy of users who aren't
developers.

Next | Query returned 21 messages, browsing 1 to 10 | Previous