All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Kanavin <alex.kanavin@gmail.com>
To: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
Cc: "poky@lists.yoctoproject.org" <poky@lists.yoctoproject.org>,
	Alexander Kanavin <alex@linutronix.de>
Subject: Re: [poky] [PATCH 2/2] meta-poky/conf/templates/default/conf-description.txt: add a template description
Date: Thu, 31 Aug 2023 19:11:52 +0200	[thread overview]
Message-ID: <CANNYZj_5aXePxpBMw9evwWV7krAa9cCgwDuyewmd+0U4gaMwKQ@mail.gmail.com> (raw)
In-Reply-To: <DB5PR02MB102135CCC4F1841B25E51AF8CEFE5A@DB5PR02MB10213.eurprd02.prod.outlook.com>

On Thu, 31 Aug 2023 at 19:04, Peter Kjellerstedt
<peter.kjellerstedt@axis.com> wrote:
> > +++ b/meta-poky/conf/templates/default/conf-description.txt
> > @@ -0,0 +1 @@
> > +This is the default build configuration for the Poky reference distribution.
> > --
> > 2.30.2
>
> To use the same nomenclature as for the variables, how about calling
> this conf-summary.txt instead? Compare to SUMMARY vs DESCRIPTION.

To match them up we'd also have to rename conf-notes.txt, breaking
compatiblity. And the meanings are not the same as in
summary/description recipes or package metadata.

conf-notes.txt would contain lengthy instructions/notes for how to use
the template and would be shown when you actually set up a build
directory (this is already happening now), conf-description.txt has a
single sentence saying what it is for, and shown before/during
selection of the template.

Alex


  reply	other threads:[~2023-08-31 17:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-30 14:15 [PATCH 1/2] meta/conf/templates/default/conf-notes.txt: remove Alexander Kanavin
2023-08-30 14:15 ` [PATCH 2/2] meta-poky/conf/templates/default/conf-description.txt: add a template description Alexander Kanavin
2023-08-31 17:03   ` [poky] " Peter Kjellerstedt
2023-08-31 17:11     ` Alexander Kanavin [this message]
2023-08-31 19:10       ` Peter Kjellerstedt
2023-09-01  9:24         ` Alexander Kanavin

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=CANNYZj_5aXePxpBMw9evwWV7krAa9cCgwDuyewmd+0U4gaMwKQ@mail.gmail.com \
    --to=alex.kanavin@gmail.com \
    --cc=alex@linutronix.de \
    --cc=peter.kjellerstedt@axis.com \
    --cc=poky@lists.yoctoproject.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 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.