From: Henning Schild <henning.schild@siemens.com>
To: "Roberto A. Foglietta" <roberto.foglietta@gmail.com>
Cc: isar-users@googlegroups.com
Subject: Re: [PATCH] dpkg class sbuild allows extra arguments by vars
Date: Tue, 3 Jan 2023 21:26:15 +0100 [thread overview]
Message-ID: <20230103212615.66dec94c@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <CAJGKYO6ijYqooyoKG1mgbH5ysFKbqsL0RMHpXCDkEad+gGkYAA@mail.gmail.com>
Again can you please send you patches in a way that they can actually
be reviewed in a mail based workflow.
You have conducted reviews yourself already so you should know how
things should work.
Am Tue, 3 Jan 2023 20:58:15 +0100
schrieb "Roberto A. Foglietta" <roberto.foglietta@gmail.com>:
> Hi all,
>
> Sometimes it is necessary to add some extra commands or arguments to
> sbuild but create a class into an upper layer just for this breaks
> the updates. So, this patch allows setting extra parameters through
> two variables.
>
> Signed-off-by: Roberto A. Foglietta <roberto.foglietta@gmail.com>
> ---
> meta/classes/dpkg.bbclass | 7 +++++--
> 1 file changed, 5 insertions(+), 2 deletions(-)
>
> https://github.com/ilbers/isar/commit/7e72921747aedf588af492be95fb0b91ad70f455
I can not reply to that nor to a specific line in the attachment. So
this can not be reviewed ... and therefore not approved.
I would have comments on this one that would likely require you to send
a v2. But i will just say NACK, because you deny the review again after
being asked countless times to send your patches in a proper way.
Henning
next prev parent reply other threads:[~2023-01-03 20:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-03 19:58 Roberto A. Foglietta
2023-01-03 20:26 ` Henning Schild [this message]
2023-01-03 21:39 ` Roberto A. Foglietta
2023-01-04 7:53 ` Henning Schild
2023-01-05 17:43 ` Roberto A. Foglietta
2023-01-05 18:31 ` Henning Schild
2023-01-05 18:43 ` Roberto A. Foglietta
2023-01-25 12:27 ` Uladzimir Bely
2023-01-25 16:12 ` Roberto A. Foglietta
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=20230103212615.66dec94c@md1za8fc.ad001.siemens.net \
--to=henning.schild@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=roberto.foglietta@gmail.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