aboutsummaryrefslogtreecommitdiffstats
path: root/x11-toolkits/rep-gtk2
ModeNameSize
-rw-r--r--Makefile991logstatsplainblame
-rw-r--r--distinfo61logstatsplainblame
-rw-r--r--pkg-comment38logstatsplainblame
-rw-r--r--pkg-descr76logstatsplainblame
-rw-r--r--pkg-plist2029logstatsplainblame
generated by cgit (git 2.34.1) at 2025-02-12 19:34:33 +0800
>marcus2007-12-121-1/+1 * Lock the tree for tagging.marcus2007-12-121-1/+1 * Release the lock on the ports tree.marcus2007-10-251-1/+1 * Lock the ports tree as GNOME 2.20 is nigh, and will touch quite a few ports.marcus2007-10-251-1/+1 * The ports tree is now unlocked since X.Org 7.2 was imported. However, it ismarcus2007-05-201-1/+1 * Add remko to the list of allowed committers so that he can do vuxmlcperciva2007-05-071-1/+1 * Lock the ports tree out except to portmgr, flz, lesi, simon, and cperciva.marcus2007-05-041-1/+1 * Unlock the ports tree now that the RELEASE_6_2_0 tag has been set.marcus2006-10-311-1/+1 * Lock the tree down for release tagging.marcus2006-10-311-1/+1 * Re-open the tree now that the GNOME 2.16 import is done.marcus2006-10-141-1/+1 * Open the tree to ahze and mezz for GNOME help.marcus2006-10-141-1/+1 * Lock the ports tree out for GNOME 2.16 import.marcus2006-10-141-1/+1 * Release the lock on the ports tree now that GNOME 2.14 is in.marcus2006-04-301-1/+1 * Lock the ports tree for the GNOME 2.14 import.marcus2006-04-301-1/+1 * Unlock the ports tree after the GNOME 2.12 merge as most of the work ismarcus2005-11-051-1/+1 * Lock the ports tree for the GNOME 2.12 merge.marcus2005-11-051-1/+1 * Tagging is complete.krion2005-08-281-1/+1 * Lock out the ports tree for 6.0-RELEASE tagging.krion2005-08-281-1/+1 * Tagging is completekris2005-04-021-1/+1 * Lock out the ports tree for 5.4-RELEASE taggingkris2005-04-021-1/+1 * Unlock the ports tree after the big GNOME 2.10 import.marcus2005-03-121-1/+1 * Lock out the tree for the GNOME 2.10 commit.marcus2005-03-121-1/+1 * The freeze is over,kris2005-01-081-1/+1 * Lock out ports tree for 4.11-RELEASE taggingkris2005-01-081-1/+1 * Unlock the tree now that the big GNOME 2.8 stuff is done.marcus2004-11-081-1/+1 * Lock out the ports tree for the GNOME 2.8 update, and all the resultingmarcus2004-11-081-1/+1 * Tagging is completekris2004-10-121-1/+1 * Lock out the ports tree in preparation for tagging.kris2004-10-121-1/+1 * Unlock the tree now that the libtool patch is in.marcus2004-07-101-1/+1 * Lock down the ports tree temporarily to apply a big libtool patch.marcus2004-07-101-1/+1 * Unlock the ports tree after tagging it for RELEASE_4_10_0.marcus2004-04-291-1/+1 * Lock down the ports tree for RELEASE_4_10_0 tagging.marcus2004-04-281-1/+1 * Unlock the ports tree after the GNOME 2.6 merge.marcus2004-04-051-1/+1 * Lock the ports tree out while I merge GNOME 2.6.marcus2004-04-051-1/+1 * Unlock the ports tree, and prepare to be raked across the coals.marcus2004-02-041-1/+1 * Lock down the ports tree while I make the new bsd.*.mk changes.marcus2004-02-041-1/+1 * Unlock the ports tree. The ports tree is now in a semi-freeze. There shouldmarcus2003-12-041-1/+1 * Lock the ports tree for 5.2-RELEASE tagging.marcus2003-12-041-1/+1 * Unlock ports tree. Ports tree is now semi-frozen. No sweeping commitsmarcus2003-09-241-1/+1 * Lock out access to the ports tree while I prepare for 4.9-RELEASE.marcus2003-09-241-1/+1 * Remove lock on ports tree. Ports are now unfrozen, but as usual pleasekris2003-06-011-1/+1 * Lock out access to the ports collection while I work on preparing it forkris2003-05-231-1/+1 * Unlock ports tree after taggingkris2003-03-221-1/+1 * Lock out ports tree in preparation for tagging of 4.8-RELEASEkris2003-03-221-1/+1 * Allow a per-repo box as well as a global onepeter2003-03-191-1/+1 * Catch up to projects/peter2003-02-281-9/+0 * Actually use the meisters group. I hope.peter2003-01-091-0/+1 * Release lock on ports collection.kris2003-01-011-1/+1 * Lock out the ports tree for RELEASE_5_0_0 taggingkris2003-01-01