Hi Eygene, I think it would be more efficient if individuals who have discovered these issues could submit the patches directly to the corresponding port maintainers.
You could also file a PR for tracking purposes. In any case, please cc: me so that I am aware of these breakage and in case I need to resolve any non-trivial mapping. Thank you. -- Qing > -----Original Message----- > From: rea-f...@codelabs.ru [mailto:rea-f...@codelabs.ru] > Sent: Monday, December 22, 2008 2:41 AM > To: Li, Qing > Cc: freebsd-curr...@freebsd.org; freebsd-net@freebsd.org; Gerald > Pfeifer; Vladimir Grebenschikov; Kip Macy; Qing Li; Ian FREISLICH; > Erwin Lansing > Subject: Re: HEADSUP: arp-v2 has been committed > > Li, good day. > > Mon, Dec 22, 2008 at 01:55:34AM -0800, Li, Qing wrote: > > Thank you all for patching these programs. > > Thank you for your work! > > > I scanned through your patches and they all look fine. > > Each one that I read through seems to be simple fix, which > > is what I hoped for. > > Are you going to submit the patches for affected ports by yourself > or individual persons should do it? For me, it does not matter > what route you will take, I just want to know how to proceed ;)) > -- > Eygene > _ ___ _.--. # > \`.|\..----...-'` `-._.-'_.-'` # Remember that it is hard > / ' ` , __.--' # to read the on-line manual > )/' _/ \ `-_, / # while single-stepping the kernel. > `-'" `"\_ ,_.-;_.-\_ ', fsc/as # > _.-'_./ {_.' ; / # -- FreeBSD Developers handbook > {_.-``-' {_/ # _______________________________________________ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
