Re: [PATCH v5 37/37] memprofiling: Documentation

[Randy Dunlap]

On 3/7/24 10:17, Kent Overstreet wrote:
> On Wed, Mar 06, 2024 at 07:18:57PM -0800, Randy Dunlap wrote:
>> Hi,
>> This includes some editing suggestions and some doc build fixes.
>>
>>

[snip]

>>> +===================
>>> +Theory of operation
>>> +===================
>>> +
>>> +Memory allocation profiling builds off of code tagging, which is a library for
>>> +declaring static structs (that typcially describe a file and line number in
>>
>>                                   typically
>>
>>> +some way, hence code tagging) and then finding and operating on them at runtime
>>
>>                                                                         at runtime,
>>
>>> +- i.e. iterating over them to print them in debugfs/procfs.
>>
>>   i.e., iterating
> 
> i.e. latin id est, that is: grammatically my version is fine
> 

Some of my web search hits say that a comma is required after "i.e.".
At least one of them says that it is optional.
And one says that it is not required in British English.

But writing it with "that is":


hence code tagging) and then finding and operating on them at runtime
- that is iterating over them to print them in debugfs/procfs.

is not good IMO. But it's your document.


-- 
#Randy