Date: Thu, 19 Feb 2009 16:44:45 -0800 From: George Hartzell <hartzell@alerce.com> To: Pawel Jakub Dawidek <pjd@FreeBSD.org> Cc: freebsd-fs@freebsd.org, goran.lowkrantz@ismobile.com, Roman Divacky <rdivacky@freebsd.org>, freebsd-current@freebsd.org, George Hartzell <hartzell@alerce.com> Subject: Re: Patch for 'zfs send -R' core dump (pr bin/130105) Message-ID: <18845.64765.71312.244570@almost.alerce.com> In-Reply-To: <20090219203541.GB2083@garage.freebsd.pl> References: <18845.40641.33220.936902@almost.alerce.com> <20090219181114.GA57360@freebsd.org> <20090219203541.GB2083@garage.freebsd.pl>
next in thread | previous in thread | raw e-mail | index | archive | help
Pawel Jakub Dawidek writes: > On Thu, Feb 19, 2009 at 07:11:14PM +0100, Roman Divacky wrote: > > > > btw.... I track the opensolaris hg at work and there's a quite a few commits > > to zfs (almost) every week. fixing coredumps and other problems. > > > > maybe we can track the opensolaris a little closer? > > It is beeing tracked very close, I'd say, in perforce > (//depot/user/pjd/zfs/...). > > The problem is that trivial fixes are mixed with very intrusive changes, > so it is too risky to track it even in HEAD (I'm running HEAD on my > ZFS-only laptop!). OpenSolaris development is also very different from > FreeBSD's. We use to describe every single change very carefully in > commit logs, where OpenSolaris commits are based only on bug number and > bug descriptions. Many changes are committed at once, so it is hard to > pick only some changes. Is it possible for fixes like the one that I posted to get merged into -CURRENT w/out waiting for your next mega-relase? On the one hand it would be very useful, on the other I can imagine that if it happens too often it would make your life difficult. g.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?18845.64765.71312.244570>