From: Uladzimir Bely <ubely@ilbers.de>
To: srinu <srinuvasan.a@siemens.com>,
isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH] debianize: introduce DEBIAN_PROVIDES and DEBIAN_REPLACES
Date: Mon, 04 Mar 2024 15:15:52 +0300 [thread overview]
Message-ID: <3fff3c08f7da69341fa08ca7cd1273bf80d93e5a.camel@ilbers.de> (raw)
In-Reply-To: <81ce86e1-521f-44f5-977a-ce799eec10c1n@googlegroups.com>
On Sun, 2024-03-03 at 22:08 -0800, 'srinu' via isar-users wrote:
> Hi Uladzimir,
>
> Can you please merge this changes if no objection.
>
> Thanks,
> Srinu
>
Hello Srinuvasan,
We are going to perform a new release today. All the targets were
already tested and adding any new patches on top will results in
postponing the release.
As your patch is not a fix but improvement we plan to apply it right
after the tagging.
> On Wednesday, February 28, 2024 at 3:11:58 PM UTC+5:30
> srinuv...@siemens.com wrote:
> > From: Srinuvasan A <srinuv...@siemens.com>
> >
> > Allow setting the Provides and Replaces field for auto generated
> > control files,
> > with this changes now user can configure the provides and replaces
> > in the debian/control file.
> >
> > Recipes can simply setting the Provides and Replaces field now by
> > defining the
> > DEBIAN_PROVIDES and DEBIAN_REPLACES variable.
> >
> > Signed-off-by: Srinuvasan A <srinuv...@siemens.com>
next prev parent reply other threads:[~2024-03-04 12:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-28 9:41 srinuvasan.a
2024-03-04 6:08 ` srinu
2024-03-04 12:15 ` Uladzimir Bely [this message]
2024-03-06 7:20 ` Uladzimir Bely
-- strict thread matches above, loose matches on Subject: below --
2024-02-13 12:56 [PATCH] debianize: Introduce " Srinuvasan Arjunan
2024-02-13 18:48 ` Florian Bezdeka
2024-02-16 6:38 ` Uladzimir Bely
2023-11-14 19:05 [PATCH] debianize: introduce " Cedric Hombourger
2023-11-16 7:07 ` Uladzimir Bely
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=3fff3c08f7da69341fa08ca7cd1273bf80d93e5a.camel@ilbers.de \
--to=ubely@ilbers.de \
--cc=isar-users@googlegroups.com \
--cc=srinuvasan.a@siemens.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