From: Metin Kaya <metin.kaya@arm.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-trace-devel@vger.kernel.org
Subject: Re: [PATCH] libtracefs .gitignore: Ignore utest/trace-utest in git
Date: Thu, 17 Oct 2024 09:19:41 +0100 [thread overview]
Message-ID: <51073f99-b44f-415b-b50d-9a1b71383280@arm.com> (raw)
In-Reply-To: <20241016125115.4f48dc88@gandalf.local.home>
On 16/10/2024 5:51 pm, Steven Rostedt wrote:
> On Tue, 15 Oct 2024 16:45:02 +0100
> Metin Kaya <metin.kaya@arm.com> wrote:
>
> I'm applying this, but even the most trivial patches must have a commit
> log. There should never be an empty commit log (except for whitespace and
> spelling fixes).
Exactly. I kind of had lack of creativity while writing the commit.
>
> I added this:
>
> The test program utest/trace-utest is created by "make test" and should
> not be tracked by git.
Thank you! Will copy this to my other .gitignore patch in trace-cmd [1].
[1]
https://lore.kernel.org/linux-trace-devel/20241015154413.4189532-1-metin.kaya@arm.com
>
> -- Steve
>
>
>> Signed-off-by: Metin Kaya <metin.kaya@arm.com>
>> ---
>> .gitignore | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/.gitignore b/.gitignore
>> index 3e72a58..7e61473 100644
>> --- a/.gitignore
>> +++ b/.gitignore
>> @@ -13,3 +13,4 @@ tfs_version.h
>> *.o
>> .*.d
>> sqlhist
>> +utest/trace-utest
>
prev parent reply other threads:[~2024-10-17 8:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-15 15:45 [PATCH] libtracefs .gitignore: Ignore utest/trace-utest in git Metin Kaya
2024-10-16 16:51 ` Steven Rostedt
2024-10-17 8:19 ` Metin Kaya [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=51073f99-b44f-415b-b50d-9a1b71383280@arm.com \
--to=metin.kaya@arm.com \
--cc=linux-trace-devel@vger.kernel.org \
--cc=rostedt@goodmis.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).