From: compudj@krystal.dyndns.org (Mathieu Desnoyers)
Subject: [ltt-dev] LTTng-UST -> UST
Date: Wed, 1 Sep 2010 11:39:19 -0400 [thread overview]
Message-ID: <20100901153918.GA25435@Krystal> (raw)
In-Reply-To: <alpine.DEB.2.00.1009011650500.19120@as68123.uab.ericsson.se>
Agreed, different names would be good. Sticking with a "LTT" derivative
has hurt the LTTng project more than anything else in terms of
mainlining into the Linux kernel. Some kernel developers don't care if
it's a complete re-write, they remember old fights.
So I'm fine with "UST", as long as we specify somewhere in the project
page that it is a port of the kernel lttng to userspace.
I actually pointed that out a while ago when the TMF project were
starting to simply use "LTTng" to name their viewer module. It seems
like they still use that name alone sometimes, which can cause some
degree of confusion. "LTTng viewer plugin" seems to be too long to spell
out.
Thanks,
Mathieu
* Nils Carlson (nils.carlson at ericsson.com) wrote:
> Maybe the problem is in my head... :-) I'm actually just talking about
> the title on the webpage, code and manuals already just say UST mostly.
>
> My problem is that managers are going to the UST website and noting
> LTTng-UST. Then they shorten it to LTTng (as they don't know better)
> which confuses everyone who knows about LTTng (the patches on the
> kernel). Then, once it's been explained to them about the kernel, and
> userspace, and how they're different and separate and so on they start
> coming up with new things. Yesterday I managed to stop one of them
> writing down LTTng-KST (kernelspace tracer). :-/
>
> So, sorry for all the commotion.
>
> But maybe in the long-term we don't want to be called LTTng-UST? It's a
> bit of a mouthfull and UST is short and sweet and doesn't share even part
> of the name with another project. It's also better from a marketing
> perspective. Just changing the title on the webpage and changing the
> README would pretty much do it.
>
> /Nils
>
> On Wed, 1 Sep 2010, Pierre-Marc Fournier wrote:
>
>> Hi Nils,
>>
>> I'm not sure I understand the problem you are referring to.
>>
>> You are always free to say just UST, the tarballs are called ust.tar.gz, the Debian package name is ust.
>>
>> In what context do you see the project called LTTng-UST? Do you feel that it comes from the website? Are you proposing a separate website be made for ust?
>>
>> pmf
>>
>> ----- Original message -----
>>> When discussing LTTng-UST I very often run into some confusion about the
>>> name, specifically people assume I'm talking about LTTng. In order to
>>> reduce the amount of confusion I suggest we rename LTTng-UST to just UST.
>>>
>>> Pierre-Marc, Mathieu, everyone else, any comments?
>>> /Nils
>>>
>>
>>
>
> _______________________________________________
> ltt-dev mailing list
> ltt-dev at lists.casi.polymtl.ca
> http://lists.casi.polymtl.ca/cgi-bin/mailman/listinfo/ltt-dev
>
--
Mathieu Desnoyers
Operating System Efficiency R&D Consultant
EfficiOS Inc.
http://www.efficios.com
next prev parent reply other threads:[~2010-09-01 15:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-01 10:52 Nils Carlson
2010-09-01 10:52 ` Nils Carlson
2010-09-01 10:52 ` Nils Carlson
2010-09-01 12:51 ` David Goulet
2010-09-01 13:24 ` Pierre-Marc Fournier
2010-09-01 15:00 ` Nils Carlson
2010-09-01 15:39 ` Mathieu Desnoyers [this message]
2010-09-01 17:11 ` Pierre-Marc Fournier
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=20100901153918.GA25435@Krystal \
--to=compudj@krystal.dyndns.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