public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Florian Bezdeka <florian.bezdeka@siemens.com>
To: Srinuvasan Arjunan <srinuvasan_a@mentor.com>,
	isar-users@googlegroups.com
Cc: cedric.hombourger@siemens.com, Srinuvasan <srinuvasan.a@siemens.com>
Subject: Re: [PATCH] debianize: Introduce DEBIAN_PROVIDES and DEBIAN_REPLACES
Date: Tue, 13 Feb 2024 19:48:47 +0100	[thread overview]
Message-ID: <fc3534c46d91e4739f7e6aa3c3e1bc3a242246b9.camel@siemens.com> (raw)
In-Reply-To: <20240213125605.1964664-1-srinuvasan_a@mentor.com>

On Tue, 2024-02-13 at 18:26 +0530, Srinuvasan Arjunan wrote:
> From: Srinuvasan <srinuvasan.a@siemens.com>

Something is wrong with your mail setup. The From: header 
is "Srinuvasan Arjunan <srinuvasan_a@mentor.com>" while your singed-
off-by and the From: part of the body is set to "Srinuvasan
<srinuvasan.a@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 <srinuvasan.a@siemens.com>


  reply	other threads:[~2024-02-13 18:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-13 12:56 Srinuvasan Arjunan
2024-02-13 18:48 ` Florian Bezdeka [this message]
2024-02-16  6:38 ` Uladzimir Bely
  -- strict thread matches above, loose matches on Subject: below --
2024-02-28  9:41 [PATCH] debianize: introduce " srinuvasan.a
2024-03-04  6:08 ` srinu
2024-03-04 12:15   ` Uladzimir Bely
2024-03-06  7:20 ` Uladzimir Bely
2023-11-14 19:05 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=fc3534c46d91e4739f7e6aa3c3e1bc3a242246b9.camel@siemens.com \
    --to=florian.bezdeka@siemens.com \
    --cc=cedric.hombourger@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=srinuvasan.a@siemens.com \
    --cc=srinuvasan_a@mentor.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