Re: qe missing config reference to if_uba

Argh! mrg, not nrg. (sorry)

And to be clear, netbsd 10.1 is still on the netbsd-10 branch, as will 
any further releases of version 10.

Try to visualize development as going on in current, which is main, 
which isn't a branch. Then when a new major version of netbsd is 
released, a branch is created on which all further development for any 
update to that version of netbsd will be done on. Which is work that is 
done in parallel with further development of current.

Any specific release is then also tagged, so you can easily check out 
any specific version you are interested in, but those tags are then 
along the line on the branch.

   Johnny

On 2025-04-23 16:37, Johnny Billquist wrote:
> netbsd-10 is already a branch. Any work on current will never show up an 
> a branch unless an explicit pull is done into that branch, which is what 
> nrg was asking about.
> 
>    Johnny
> 
> On 2025-04-23 16:16, Josh Moyer wrote:
>> [ Ragge/Johnny/port-vax seniors: can you add your comment(s), please? ]
>>
>>> .mrg. wrote:
>>>>> Josh wrote:
>>>>> -device qt: ifnet, ether, arp
>>>>> +device qt: ifnet, ether, arp, ifuba
>>>
>>> ah, this one was fixed by rin back in october.
>>> are you using netbsd-10?  do you want pullups for these?
>>
>> I am using NetBSD 10.1 with the corresponding kernel source tarball 
>> and so was surprised that I didn't have the qt fix and thought my 
>> source tree was out of date. (!)
>>
>> However and per cvsweb, the fix by Rin is dated Oct 21, 2024.  I 
>> double checked the tarball, fetching a fresh copy from cdn.netbsd.org 
>> [1], and it contains dev/qbus/files.uba version 1.17, dated Mar 11, 
>> 2008.  10.1 was released Dec 16, 2024.  I wasn't sure how tocheck 
>> when 10.1 was frozen/forked or whatever and so am unsure if the source 
>> tarball is missing Rin's fix due to an oversight or due to branching/ 
>> forking/release practices.
>>
>> As for pullups, I'm not completely clear on what those are.  Since 
>> these drivers are included in GENERIC and because the fix for those 
>> compiling a custom kernel is "easy" and well documented here at this 
>> point, I don't see any reason for special handling/inclusion/ 
>> publication and feel that the standard handling/release process is 
>> probably ok.  But, again, I'm a little unclear of the particulars.  
>> Maybe one of the more senior port-vax participants like Johnny or 
>> Ragge should comment here?
>>
>> [1] https://cdn.netbsd.org/pub/NetBSD/NetBSD-10.1/source/sets/syssrc.tgz
>>
>> Ps.  What mailer do you use/recommend for quoting?  Outlook,sadly 
>> (don't laugh), is not very good at it, it seems.
>>
>> -- 
>> Kind regards,
>> Josh/NODOMAIN.NET
>>
>> -----Original Message-----
>> From: matthew green <[email protected]>
>> Sent: Tuesday, April 22, 2025 6:25 PM
>> To: Josh Moyer <[email protected]>
>> Cc: [email protected]
>> Subject: re: qe missing config reference to if_uba
>>
>>>> -device qt: ifnet, ether, arp
>>>> +device qt: ifnet, ether, arp, ifuba
>>
>> ah, this one was fixed by rin back in october.
>>
>> are you using netbsd-10?  do you want pullups for these?
>>
>>
>> .mrg.
> 

-- 
Johnny Billquist                  || "I'm on a bus
                                   ||  on a psychedelic trip
email: [email protected]             ||  Reading murder books
pdp is alive!                     ||  tryin' to stay hip" - B. Idol