All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Sapp, Randolph" <rs@ti.com>
To: Denys Dmytriyenko <denis@denix.org>
Cc: <reatmon@ti.com>, <meta-ti@lists.yoctoproject.org>
Subject: Re: [EXTERNAL] Re: [meta-ti] [dunfell][PATCH] ti-img-rogue-*: Bump the graphics recipes
Date: Wed, 12 Oct 2022 11:32:55 -0500	[thread overview]
Message-ID: <VAFNJR.UICQIQVLHTVW2@ti.com> (raw)
In-Reply-To: <20221011231649.GE22689@denix.org>

On Tue, Oct 11 2022 at 07:16:49 PM -0400, Denys Dmytriyenko 
<denis@denix.org> wrote:
> Should these be mentioned in the git commit message?

Depends on what we're actually trying to track in these commit 
messages. As far as I'm concerned these commit messages should only 
track changes to the recipes and reasoning, but if you believe they 
should also track upstream change notes then I will modify it 
accordingly.




  reply	other threads:[~2022-10-12 16:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-06 23:41 [dunfell][PATCH] ti-img-rogue-*: Bump the graphics recipes Randolph Sapp
2022-10-11  1:44 ` [meta-ti] " Denys Dmytriyenko
2022-10-11 21:20   ` [EXTERNAL] " Sapp, Randolph
2022-10-11 23:16     ` Denys Dmytriyenko
2022-10-12 16:32       ` Sapp, Randolph [this message]
2022-10-12 17:28         ` [EXTERNAL] " Denys Dmytriyenko
2022-10-12 17:43           ` [EXTERNAL] " Sapp, Randolph

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=VAFNJR.UICQIQVLHTVW2@ti.com \
    --to=rs@ti.com \
    --cc=denis@denix.org \
    --cc=meta-ti@lists.yoctoproject.org \
    --cc=reatmon@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.