From: Steven Rostedt <rostedt@goodmis.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
Cc: linux-trace-devel@vger.kernel.org
Subject: Re: [PATCH 1/2] libtracefs: clean also docs by default
Date: Fri, 4 Feb 2022 08:21:32 -0500 [thread overview]
Message-ID: <20220204082132.57be9bab@rorschach.local.home> (raw)
In-Reply-To: <652ddddb-6770-ca49-d00e-3b24ebc602a4@canonical.com>
On Fri, 4 Feb 2022 09:59:06 +0100
Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com> wrote:
> I don't know actually, but I find natural that clean removes all
> objects, even ones not created by "make all".
The main reason I like to keep documentation clean and code clean
separate, is because when I develop between different branches,
checking out an older one then a newer one, the make dependencies can
get screwed up. A make clean usually solves the issue when that
happens. But I don't want to rebuild the documentation every time I do
a make clean.
>
> I see your point, so I do not insist on this solution. I can fix the
> incomplete cleaning on Debian package side.
>
Great. I'll take the second patch and drop this one then.
Thanks for your contributions!
-- Steve
prev parent reply other threads:[~2022-02-04 13:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-24 10:52 [PATCH 1/2] libtracefs: clean also docs by default Krzysztof Kozlowski
2022-01-24 10:52 ` [PATCH 2/2] libtracefs: fix utest linking path Krzysztof Kozlowski
2022-02-04 2:44 ` Steven Rostedt
2022-02-04 2:41 ` [PATCH 1/2] libtracefs: clean also docs by default Steven Rostedt
2022-02-04 8:59 ` Krzysztof Kozlowski
2022-02-04 13:21 ` Steven Rostedt [this message]
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=20220204082132.57be9bab@rorschach.local.home \
--to=rostedt@goodmis.org \
--cc=krzysztof.kozlowski@canonical.com \
--cc=linux-trace-devel@vger.kernel.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).