From: walter harms <wharms-fPG8STNUNVg@public.gmane.org>
To: Alexei Starovoitov <ast-uqk4Ao+rVK5Wk0Htik3J/w@public.gmane.org>
Cc: linux-man <linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH v2 man-pages] bpf.2: new page documenting bpf(2)
Date: Thu, 12 Mar 2015 16:50:20 +0100 [thread overview]
Message-ID: <5501B5BC.2010806@bfs.de> (raw)
In-Reply-To: <CAMEtUuxZrmqUvgBX5zNbEdExqPaNw0LUhFyGP=N9erVqeKwhSQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Am 12.03.2015 16:20, schrieb Alexei Starovoitov:
> On Thu, Mar 12, 2015 at 3:09 AM, walter harms <wharms-fPG8STNUNVg@public.gmane.org> 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
next prev parent reply other threads:[~2015-03-12 15:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-12 15:20 [PATCH v2 man-pages] bpf.2: new page documenting bpf(2) Alexei Starovoitov
[not found] ` <CAMEtUuxZrmqUvgBX5zNbEdExqPaNw0LUhFyGP=N9erVqeKwhSQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-03-12 15:50 ` walter harms [this message]
[not found] ` <5501B5BC.2010806-fPG8STNUNVg@public.gmane.org>
2015-03-12 15:51 ` Alexei Starovoitov
-- strict thread matches above, loose matches on Subject: below --
2015-03-11 4:28 Alexei Starovoitov
[not found] ` <1426048097-14726-1-git-send-email-ast-uqk4Ao+rVK5Wk0Htik3J/w@public.gmane.org>
2015-03-12 10:09 ` walter harms
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5501B5BC.2010806@bfs.de \
--to=wharms-fpg8stnunvg@public.gmane.org \
--cc=ast-uqk4Ao+rVK5Wk0Htik3J/w@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).