All of lore.kernel.org
 help / color / mirror / Atom feed
From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Daniel Vacek <neelx@suse.com>, Qu Wenruo <wqu@suse.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 2/2] btrfs-progs: gitignore: add GNUmakefile
Date: Tue, 27 Oct 2026 19:59:57 +1030	[thread overview]
Message-ID: <9d996744-fdc1-470c-b24c-98628350ecf8@gmx.com> (raw)
In-Reply-To: <CAPjX3FfVnjtKBO1LDiYXZpqHybDsE2R6r-8a++S5Z1-VR5Btww@mail.gmail.com>



在 2026/10/27 19:46, Daniel Vacek 写道:
> On Tue, 27 Oct 2026 at 09:36, Qu Wenruo <wqu@suse.com> wrote:
>> I use GNUmakefile to add extra compiling flags without modifying the
>> existing Makefile:
>>
>>   MAKEFLAGS += -j12
>>   include Makefile
>>
>> So the GNUmakefile is more or less reflecting personal tastes, better to
>> add it to gitignore.
> 
> So better to add it to gitignore I guess ;-)

Facepalm, I didn't notice what's going wrong until two lines later...
> 
> --nX
> 
>> Signed-off-by: Qu Wenruo <wqu@suse.com>
>> ---
>>   GNUmakefile | 2 ++
>>   1 file changed, 2 insertions(+)
>>   create mode 100644 GNUmakefile
>>
>> diff --git a/GNUmakefile b/GNUmakefile
>> new file mode 100644
>> index 000000000000..e0eaca65651c
>> --- /dev/null
>> +++ b/GNUmakefile
>> @@ -0,0 +1,2 @@
>> +MAKEFLAGS += -j12
>> +include Makefile
>> --
>> 2.56.0
>>
>>
> 


      reply	other threads:[~2026-10-27  9:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-27  8:35 [PATCH 0/2] btrfs-progs: simple cleanup related to LLVM (not LLM) Qu Wenruo
2026-10-27  8:35 ` [PATCH 1/2] btrfs-progs: remove set but unused variables Qu Wenruo
2026-10-27  9:18   ` Daniel Vacek
2026-10-27  8:35 ` [PATCH 2/2] btrfs-progs: gitignore: add GNUmakefile Qu Wenruo
2026-10-27  9:16   ` Daniel Vacek
2026-10-27  9:29     ` Qu Wenruo [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=9d996744-fdc1-470c-b24c-98628350ecf8@gmx.com \
    --to=quwenruo.btrfs@gmx.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=neelx@suse.com \
    --cc=wqu@suse.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.