Next | Query returned 78 messages, browsing 61 to 70 | Previous

History of commit frequency

CVS Commit History:


   2009-08-03 14:55:41 by Joerg Sonnenberger | Files touched by this commit (1)
Log message:
Correctly call PY_COMPILE_ALL
   2009-07-08 15:56:01 by Joerg Sonnenberger | Files touched by this commit (15)
Log message:
Provide PY_COMPILE_ALL and PY_COMPILE_O_ALL to compile all Python
sources in a directory (tree) in pversion.mk. Adjust the various places
that called it locally.
   2009-06-15 00:00:42 by Joerg Sonnenberger | Files touched by this commit (316)
Log message:
Convert @exec/@unexec to @pkgdir or drop it.
   2009-02-09 23:56:28 by Joerg Sonnenberger | Files touched by this commit (167)
Log message:
Switch to Python 2.5 as default. Bump revision of all packages that have
changed runtime dependencies now.
   2008-06-20 03:09:45 by Joerg Sonnenberger | Files touched by this commit (993)
Log message:
Add DESTDIR support.
   2007-09-21 15:04:45 by Thomas Klausner | Files touched by this commit (483)
Log message:
Fix paths for GConf, libglade, libart, libsigc++, lablgtk moves.
Bump PKGREVISION.
   2006-05-08 15:09:39 by Matthias Drochner | Files touched by this commit (4) | Package updated
Log message:
fix some path substitution so that that thing finally works,
and update to 0.6 which brings some UI fixes and improvents
   2006-04-22 11:22:18 by Roland Illig | Files touched by this commit (231)
Log message:
Removed the superfluous "quotes" and 'quotes' from variables that don't
need them, for example RESTRICTED and SUBST_MESSAGE.*.
   2006-04-17 15:47:02 by Thomas Klausner | Files touched by this commit (1055) | Package updated
Log message:
Bump BUILDLINK_ABI_DEPENDS.png and PKGREVISION for png-1.2.9nb2 update.
   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 78 messages, browsing 61 to 70 | Previous