From: Harald Servat <harald.servat@bsc.es>
To: Vince Weaver <vincent.weaver@maine.edu>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: Referencing perf?
Date: Tue, 13 May 2014 17:34:53 +0200 [thread overview]
Message-ID: <53723B9D.40800@bsc.es> (raw)
In-Reply-To: <alpine.DEB.2.10.1405131021440.24957@vincent-weaver-1.umelst.maine.edu>
On 13/05/14 16:24, Vince Weaver wrote:
> On Sat, 10 May 2014, Harald Servat wrote:
>
>> which is the appropriate way to reference perf in a publication?
>
> That's a good question.
>
> The original authors are T. Gleixner and I. Molnar, but they've never
> published a real document about it. You could try citing the
> tools/perf/design.txt document that comes with the Linux kernel,
> or also the git commit 0793a61d4df8daeac6492dbf8d2f3e5713caae5e
> from Thu Dec 4 2008 that introduced perf_event to the world.
>
> I'm not sure if there is an official way to cite a git commit.
Thank you very much, Vince.
> Vince
>
WARNING / LEGAL TEXT: This message is intended only for the use of the
individual or entity to which it is addressed and may contain
information which is privileged, confidential, proprietary, or exempt
from disclosure under applicable law. If you are not the intended
recipient or the person responsible for delivering the message to the
intended recipient, you are strictly prohibited from disclosing,
distributing, copying, or in any way using this message. If you have
received this communication in error, please notify the sender and
destroy and delete any copies you may have received.
http://www.bsc.es/disclaimer
next prev parent reply other threads:[~2014-05-13 15:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-10 17:54 Referencing perf? Harald Servat
2014-05-13 14:24 ` Vince Weaver
2014-05-13 15:34 ` Harald Servat [this message]
2014-05-14 0:43 ` Namhyung Kim
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=53723B9D.40800@bsc.es \
--to=harald.servat@bsc.es \
--cc=linux-perf-users@vger.kernel.org \
--cc=vincent.weaver@maine.edu \
/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).