poky.lists.yoctoproject.org archive mirror
 help / color / mirror / Atom feed
From: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
	Bruce Ashfield <bruce.ashfield@gmail.com>
Cc: "poky@lists.yoctoproject.org" <poky@lists.yoctoproject.org>
Subject: RE: [poky] [PATCH] poky.conf: Set the distro name to "scarthgap"
Date: Thu, 7 Mar 2024 14:51:35 +0000	[thread overview]
Message-ID: <DB5PR02MB10213F36627AE035945059A7DEF202@DB5PR02MB10213.eurprd02.prod.outlook.com> (raw)
In-Reply-To: <6961d89a8613fedbd3893385b23c4d6687560c41.camel@linuxfoundation.org>

> -----Original Message-----
> From: poky@lists.yoctoproject.org <poky@lists.yoctoproject.org> On Behalf
> Of Richard Purdie
> Sent: den 6 mars 2024 23:52
> To: Peter Kjellerstedt <peter.kjellerstedt@axis.com>; Bruce Ashfield
> <bruce.ashfield@gmail.com>
> Cc: poky@lists.yoctoproject.org
> Subject: Re: [poky] [PATCH] poky.conf: Set the distro name to "scarthgap"
> 
> On Wed, 2024-03-06 at 08:59 -0800, Peter Kjellerstedt wrote:
> > I am just following the established procedure for integrating changes
> > to OE: send a patch, wait for it to be accepted or receive feedback,
> > if nothing happens within a reasonable time frame (where I typically
> > wait about a week), then ping the patch as it may have been missed.
> >
> > Since I expect us to be using M3 to do our preparations for the
> > upcoming release, I thought it appropriate to give the patch a little
> > nudge since simple things like this are easily overlooked when
> > focusing on the more problematic integrations.
> >
> > And the reason I sent it as a patch rather than a request to go and
> > change the value is because I assume it is a faster/easier process to
> > take a prepared patch rather than to manually do the change (even if
> > it is just a one line change like this).
> >
> > > Richard obviously knows what has to be done to prepare for a
> > > release, and if it hasn't been done yet, there are likely reasons
> > > for that.
> 
> As Bruce suspects, I do have scripts that do a variety of these things
> for releases. They're not nice well written scripts and make
> assumptions about state. My local trees are in such a mess due to
> ongoing integration issues I don't dare run them atm and if I take the
> patches, I then have to resolve the conflicts with the scripts as well.
> Most of that is because I have code which I don't know whether we're
> going to end up merging or not and it has implications on the helper
> branches and autobuilder config.

Ok, I understand. 

> 
> Basically, the bottom line is there are many different problems, lots
> of people want my time and I just can't do everything. This one hasn't
> made it to a priority high enough to spend time on fixing :/.
> 
> Cheers,
> 
> Richard

I should be able to force an override for it in our Scarthgap-adaptation 
layer so we will manage even if this is not in place for M3.

//Peter


      reply	other threads:[~2024-03-07 14:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <17B7D3DE94B664C2.7754@lists.yoctoproject.org>
2024-03-06 14:11 ` [poky] [PATCH] poky.conf: Set the distro name to "scarthgap" Peter Kjellerstedt
2024-03-06 14:30   ` Bruce Ashfield
2024-03-06 15:30     ` Peter Kjellerstedt
2024-03-06 15:48       ` Bruce Ashfield
2024-03-06 16:59         ` Peter Kjellerstedt
2024-03-06 17:32           ` Bruce Ashfield
2024-03-06 22:51           ` Richard Purdie
2024-03-07 14:51             ` Peter Kjellerstedt [this message]

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=DB5PR02MB10213F36627AE035945059A7DEF202@DB5PR02MB10213.eurprd02.prod.outlook.com \
    --to=peter.kjellerstedt@axis.com \
    --cc=bruce.ashfield@gmail.com \
    --cc=poky@lists.yoctoproject.org \
    --cc=richard.purdie@linuxfoundation.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;
as well as URLs for NNTP newsgroup(s).