Status reports - why not regularly?
Jonathan T. Sage
sagejona at theatre.msu.edu
Tue Jan 13 10:29:45 PST 2004
Kirill Ponomarew wrote:
> On Tue, Jan 13, 2004 at 07:19:11PM +0100, Josef El-Rayes wrote:
>>"Jonathan T. Sage" <sagejona at theatre.msu.edu> wrote:
>>>1. a lot of the commits are going to be ports related, and
>>>therefore dropped immediatally. this sort of report is handled
>>>wonderfully by dan @ freshports, i see no reason to duplicate
>>>what he has done
>>why excluding ports? i think important changes in the ports area
>>should be covered here too.
> As Jonathan said, the freshports is the best site where you can
> get all issues about it.
Exactally, and as Mark pointed out, I think that keeping in changes to
the ports infrastructure (bsd.ports.mk) would be an excellent idea.
"Yesterday upon the stair I saw a man
who wasn't there, he wasn't there
again today, oh how i wish he'd go away"
Rev. Jonathan T. Sage
Lighting / Set Designer
Professional Web Design
[sagejona at theatre.msu.edu]
[See Headers for Contact Info]
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 254 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20040113/8df9eeee/attachment.bin
More information about the freebsd-current