Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 21 Jan 2012 15:19:49 +0000
From:      "Robert N. M. Watson" <rwatson@freebsd.org>
To:        Hans Petter Selasky <hselasky@c2i.net>
Cc:        "src-committers@freebsd.org" <src-committers@freebsd.org>, "re@FreeBSD.org" <re@freebsd.org>, "svn-src-stable@freebsd.org" <svn-src-stable@freebsd.org>, "svn-src-all@freebsd.org" <svn-src-all@freebsd.org>, "svn-src-stable-9@freebsd.org" <svn-src-stable-9@freebsd.org>, "Bjoern A. Zeeb" <bz@freebsd.org>
Subject:   Re: svn commit: r230302 - in stable/9/sys/dev/usb: . controller
Message-ID:  <7E058E8B-EB49-4A72-8555-A15E358C09F8@freebsd.org>
In-Reply-To: <201201211433.30626.hselasky@c2i.net>
References:  <201201211344.05511.hselasky@c2i.net> <03DEA3A3-E5E4-4313-B82B-F0AD44F50ECD@FreeBSD.org> <201201211433.30626.hselasky@c2i.net>

next in thread | previous in thread | raw e-mail | index | archive | help

On 21 Jan 2012, at 13:33, Hans Petter Selasky wrote:

>>>> Just to clarify, are you saying that:
>>>>=20
>>>> (1) We should not ever do an errata note + binary update for the =
most
>>>> important of these bug fixes, just wait for them to ship in FreeBSD
>>>> 8.3/9.1?
>>>>=20
>>>> (2) We should do errata notes + binary updates for the most =
important of
>>>> these bug fixes, but we need to let them settle for a while to =
ensure
>>>> there are no unexpected consequences/etc?
>>>>=20
>>>> Do we think that the impact of the USB 3.0 hub issue will be =
significant
>>>> to our userbase -- e.g., excluding use of USB on many recent =
systems?
>>>=20
>>> I mean (2). I'm not familiar with the process of binary updates. =
Does
>>> that mean I should commit fixes to the release branches in SVN =
instead
>>> of the stable ones? I think I maybe need some help there. Never done
>>> that before :-)
>>=20
>> Because you cannot.   It would surely help if you could provide the
>> relevant part of the change as patch to re@ and you can find two =
samples
>> of ENs linked from the box in the right lower corner of the front =
page of
>> www.freebsd.org and providing parts of the text (ignore revisions etc =
for
>> now) would certainly help as well.
>=20
> Ok, I'll have a look at this once I find some time.

Sounds good -- the first step is really to let the change settle in the =
tree for a month or so to make sure we have a high confidence that it is =
without serious unfortunate side effects, and cleanly resolves any =
issues users are experiencing. Then, as Bjoern says, the next step is to =
contact re@ with a proposed patch and some draft text, and we can take =
it from there.

Robert=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7E058E8B-EB49-4A72-8555-A15E358C09F8>