Re: git: d15f2551b25f - main - rtnetlink: Report SR-IOV VF status

On 8/10/26 18:41, Lexi Winter wrote:
> hi,
> 
> Pouria Mousavizadeh Tehrani wrote in <41b8cda3-9e4f-49f1-af9b-18c04e215ab1@FreeBSD.org>:
>> On 8/9/26 10:17, Kevin Bowling wrote:
>>> The branch main has been updated by kbowling:
>>>
>>> URL: https://cgit.FreeBSD.org/src/commit/?id=d15f2551b25f79ddcbe289faa95e655100b952da
>>>
>>> commit d15f2551b25f79ddcbe289faa95e655100b952da
>>> Author:     Kevin Bowling <kbowling@FreeBSD.org>
>>> AuthorDate: 2026-08-09 02:04:11 +0000
>> [...]
>> I think we should minimize our use of nvlist(9) in the new code, especially
>> under netlink.
> 
> point of order, unrelated to this comment (although i do tend to agree):
> when replying to a long message, such as a large commit, it's helpful to
> trim the message you're replying to so it only includes relevant text,
> such as the commit message, not the entire message.
> 
> otherwise, i have to sit here holding space bar for about 5 seconds to
> scroll down to find what you actually wrote.
> 
> this isn't aimed at you specifically, since i've noticed this happening
> a few times recently.  for those of us who read all src-committers mail
> (which i guess is a large fraction of developers), some considerate
> trimming saves a lot of people a lot of time.
> 
> thank you for your consideration and please continue improving our IPv6
> stack :-) 

Side note, not an objection:

I've tended to also hit the other side of some forms of trimming:
needing to find and reference --or even quote-- what is not there any
more in what I'm reading but is spread across the message sequence.
Relevant for general reading vs. relevant for various types of replies
can be messy to judge/tradeoff. (I tend to not do well at working from
memory without review of what was written so I tend to do such finding
activities across messages more than many folks likely do.)


-- 
===
Mark Millard
marklmi at yahoo.com