On Thu, Mar 12, 2015 at 8:50 AM, walter harms <wharms@xxxxxx> wrote: > > > Am 12.03.2015 16:20, schrieb Alexei Starovoitov: >> On Thu, Mar 12, 2015 at 3:09 AM, walter harms <wharms@xxxxxx> wrote: >>> >>> >>>> +.SH DESCRIPTION >>>> +.BR bpf() >>>> +syscall is a multiplexor for a range of different operations on extended BPF >>> syscall is a multiplexor for a range of different operations on extended >>> Berkeley Packet Filter (eBPF). >>> >>> just introduce the abv. early as possible, >>> >> >> I'd rather not. The universal feedback from everyone was >> that eBPF name is ugly, awkward, hard to pronounce, hard to >> remember, hard to spell, etc. >> So I'm trying not to use it, if I can. Often when people >> say 'bpf' they mean 'extended' one and >> when they need to refer to old they say 'classic bpf'. > > it is not abut the (e) is about the BPF. you say "Berkeley Packet Filter" > a few lines later. just move that in the first line where you are using BPF > as abbreviation. It is good practice to have an explaination before using > the abrev. ahh. got it. ok. makes sense. will do. -- To unsubscribe from this list: send the line "unsubscribe linux-man" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
