Status reports - why not regularly?
josef at daemon.li
Tue Jan 13 10:42:23 PST 2004
Kirill Ponomarew <krion at FreeBSD.org> wrote:
> On Tue, Jan 13, 2004 at 01:28:27PM -0500, Jonathan T. Sage wrote:
> > Exactally, and as Mark pointed out, I think that keeping in changes to
> > the ports infrastructure (bsd.ports.mk) would be an excellent idea.
> Yes, I think portmgr@ should mail to ports@ and explain the
> most important updates to bsd.*.mk
i was rather thinking about new major ports, or big repo copies.
i think this is worth being mentioned in a report.
of course things are covered on mailinglists and freshports and
othere sites, but i think, as a summary on the whole projects work
all areas should be covered.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 479 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20040113/9751ccf1/attachment.bin
More information about the freebsd-current