Re: Rubygem .js files fubar?

2016-01-19 Thread Steve Wills
Hi, On 01/17/16 10:29 AM, Matthew Seaman wrote: > On 17/01/2016 06:33, Steve Wills wrote: >> On 01/17/16 12:57 AM, Steve Wills wrote: >>> >>> As for why the original file isn't deleted, I'm not sure. I don't see >>> this in my local tree, but I have some changes that may be masking it. >>> >> >> O

Re: Now I am aware

2016-01-19 Thread Jerry McAllister
On Tue, Jan 19, 2016 at 12:21:58PM -0500, Joe Nosay wrote: > of how self-centered and selfish all of you are. > This is a useless post. jerry > > > https://forums.freebsd.org/threads/making-it-public.54392/#post-309037 > ___ > freebsd-

Now I am aware

2016-01-19 Thread Joe Nosay
of how self-centered and selfish all of you are. https://forums.freebsd.org/threads/making-it-public.54392/#post-309037 ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to

Re: freebsd-ports Digest, Vol 661, Issue 2

2016-01-19 Thread Andrew Harris
On Tue, Jan 19, 2016 at 7:00 AM, wrote: > Send freebsd-ports mailing list submissions to > freebsd-ports@freebsd.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > or, via email, send a message with subjec

Re: PR

2016-01-19 Thread Fernando Apesteguía
On Tue, Jan 19, 2016 at 2:32 PM, Fernando Apesteguía wrote: > Hi, > > Please, can anyone take this PR? > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206294 > > Thanks in advance. And... that was fast! Thanks! ___ freebsd-ports@freebsd.org maili

PR

2016-01-19 Thread Fernando Apesteguía
Hi, Please, can anyone take this PR? https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206294 Thanks in advance. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freeb

FreeBSD ports you maintain which are out of date

2016-01-19 Thread portscout
Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you