From: Bastian Germann <bage@linutronix.de>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/1] builddeb: introduce profile excluding the dbg pkg
Date: Mon, 13 Mar 2023 11:27:33 +0100 [thread overview]
Message-ID: <f9ffe524-21be-4d35-b700-30faaa5841fc@linutronix.de> (raw)
In-Reply-To: <20230313094106.46770-1-bage@linutronix.de>
Am 13.03.23 um 10:41 schrieb Bastian Germann:
> Changelog:
> v2:
> * Align the profile name with the one that ended up in Debian.
> v3:
> * Prevent the creation of the dbg package when profile is set
Please ignore v3. Sent the wrong patches.
prev parent reply other threads:[~2023-03-13 10:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-13 9:41 [PATCH v3 0/1] builddeb: introduce profile excluding the dbg pkg Bastian Germann
2023-03-13 9:41 ` [PATCH v3 1/1] " Bastian Germann
2023-03-13 10:27 ` Bastian Germann [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=f9ffe524-21be-4d35-b700-30faaa5841fc@linutronix.de \
--to=bage@linutronix.de \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox