Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "jbouchard" <jeanbouch418@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: Package revision
Date: Mon, 07 Feb 2022 15:18:20 -0800	[thread overview]
Message-ID: <HSvl.1644275900393526587.WGPn@lists.openembedded.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 461 bytes --]

Hi,

I was wondering why the package revision are not increasing when a patch is apply to other project source, like this commit https://git.openembedded.org/openembedded-core/commit/?h=honister&id=2d3c5b078feb34cb729902292d2805c9288ebc4c. Most distribution tend to increase the package revision when such changes occur. This help to track vulnerability and bugs. I know CVE_CHECK can deal with CVE, but it is hard to track with external software.

Thanks

[-- Attachment #2: Type: text/html, Size: 645 bytes --]

             reply	other threads:[~2022-02-07 23:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-07 23:18 jbouchard [this message]
2022-02-08  9:07 ` [OE-core] Package revision Mikko.Rapeli

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=HSvl.1644275900393526587.WGPn@lists.openembedded.org \
    --to=jeanbouch418@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    /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