From mboxrd@z Thu Jan 1 00:00:00 1970 From: walter harms Subject: Re: [PATCH v2 man-pages] bpf.2: new page documenting bpf(2) Date: Thu, 12 Mar 2015 16:50:20 +0100 Message-ID: <5501B5BC.2010806@bfs.de> References: Reply-To: wharms-fPG8STNUNVg@public.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: linux-man-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Alexei Starovoitov Cc: linux-man List-Id: linux-man@vger.kernel.org Am 12.03.2015 16:20, schrieb Alexei Starovoitov: > On Thu, Mar 12, 2015 at 3:09 AM, walter harms 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. re, wh -- To unsubscribe from this list: send the line "unsubscribe linux-man" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html