Giorgos Keramidas <[EMAIL PROTECTED]> writes: > On Mon, 8 Sep 2008 14:01:25 +0200, Erwin Lansing <[EMAIL PROTECTED]> wrote: >> In preparation for both the 6.4 and 7.1 releases, the ports tree has >> been frozen. All commits have to be approved by portmgr. See the >> portmgr webpage[1] for more information about what is and isn't >> allowed during the freeze. We are aiming for a short freeze period, >> so we will be quite strict in allowing commits during the freeze. Of >> course, we do appreciate any help fixing existing errors in the tree, >> so if anyone is bored, a good starting point will be portsmon[2]. > > Damn :/ > > My emacs-22.3 release update almost made it into ports before the freeze > by 1-2 days. Is there any chance I could bribe you guys to get it in, > so we can have the latest stable 22.X GNU Emacs in the release? > > Having said that, I am a bit unfamiliar with all the work port builders > have to do during the freeze, so if getting a new Emacs in the tree is > completely out of the question because it would create a lot of work for > you guys, that's ok. > > On the other hand, if the ports stay frozen for several weeks and we > still have time to let it settle into the tree, it would be very nice to > include this version. It includes a mildly important fix in the way > Emacs spawns Python processes[1] that would be _very_ nice to have in > ports sooner, rather than a couple of months later. > > http://lists.gnu.org/archive/html/emacs-devel/2008-09/msg00215.html
Since it is a security issue it may be resolved before release. Just the patch should be polished a little. WBR -- Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone & Internet SP FreeBSD committer, http://www.FreeBSD.org The Power To Serve _______________________________________________ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
