Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: compudj@krystal.dyndns.org (Mathieu Desnoyers)
Subject: [ltt-dev] LTTV-supplied documentation
Date: Tue, 7 Sep 2010 11:46:18 -0400	[thread overview]
Message-ID: <20100907154618.GC6371@Krystal> (raw)
In-Reply-To: <4C86557B.5090408@polymtl.ca>

* Alexandre Montplaisir (alexandre.montplaisir at polymtl.ca) wrote:
> Hi,
>
> I have a question about the documentation provided with the LTTV package  
> (the /doc directory).
> Is everything in there still relevant? It's full of makefiles that don't  
> seem to "make" anything anymore.

Not everything.

>
> At first glance, the html guides in:
> doc/user/user_guide/html
> doc/developer/developer_guide/html
>
> seem to be the most up-to-date, but there's also a bunch of stuff in  
> doc/developer/ that seems relevant (provided it isn't outdated).

doc/developer contains a lot of architecture-level description of lttv,
some of which did not follow with code refactoring.

>
> As you may have guessed, I'm working on Debian packages, and was  
> wondering what should go in the "lttv-doc" one.

The documents I'm actively keeping up to date are:

/doc/developer/lttng-lttv-compatibility.txt
/LTTngManual.html

For the rest, it's a per-file investigation.

Thanks,

Mathieu


>
> Thanks,
> Alexandre
>
> _______________________________________________
> 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




  reply	other threads:[~2010-09-07 15:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-07 15:08 Alexandre Montplaisir
2010-09-07 15:46 ` Mathieu Desnoyers [this message]
2010-09-07 16:20   ` Alexandre Montplaisir
2010-09-07 16:24     ` Mathieu Desnoyers
2010-09-07 16:31       ` Alexandre Montplaisir

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=20100907154618.GC6371@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