From: Daniel Gomez <da.gomez@samsung.com>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: Luis Chamberlain <mcgrof@kernel.org>,
"kdevops@lists.linux.dev" <kdevops@lists.linux.dev>,
"gost.dev@samsung.com" <gost.dev@samsung.com>
Subject: Re: [PATCH v2 1/1] linux: generate refs automatically
Date: Fri, 23 Feb 2024 15:44:35 +0000 [thread overview]
Message-ID: <hteidenzp7hrmblujwhvdgqkjxwumvgd5n3pc2otzggsibaak2@gzn6kraunmzf> (raw)
In-Reply-To: <20240222-spotted-inescapable-crab-2cddc6@meerkat>
On Thu, Feb 22, 2024 at 12:58:24PM -0500, Konstantin Ryabitsev wrote:
> On Thu, Feb 22, 2024 at 09:03:34AM -0800, Luis Chamberlain wrote:
> > + Konstantin as he may have better ideas.
> >
> > Konstantin, this patch set enables kdevops to scrape for ref tags
> > remotely so we can dynamically generate Kconfig files used for
> > kdevops for tags which users can select. The trees users can
> > have can be on kernel.org but elsewhere. The main trees obviously
> > are Linus, the stable tree, and linux-next. For these 3 it would be
> > good to get guidance on if the below strategy of using
> >
> > git config: versionsort.suffix=-
> > git-ls-remote option: --sort=-version:refname
> >
> > is best.
>
> Why not just grab either of these two?
>
> https://kernel.org/finger_banner
> https://www.kernel.org/releases.json
This is great for latest-and-greatest. Thanks Konstantin.
Luis, I think we can integrate this json file as input for mainline, next and
stable trees and combine them with the output of git-ls-remote and yaml inputs
(if any).
>
> -K
prev parent reply other threads:[~2024-02-23 15:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20240216091829eucas1p176479ddf791b339a27aea814a553b5ff@eucas1p1.samsung.com>
2024-02-16 9:18 ` [PATCH v2 0/1] linux: generate refs automatically Daniel Gomez
[not found] ` <CGME20240216091830eucas1p1e5ee4b905b2977e2b7de54b9f4be222b@eucas1p1.samsung.com>
2024-02-16 9:18 ` [PATCH v2 1/1] " Daniel Gomez
2024-02-21 18:12 ` Luis Chamberlain
2024-02-22 16:23 ` Daniel Gomez
2024-02-22 17:03 ` Luis Chamberlain
2024-02-22 17:58 ` Konstantin Ryabitsev
2024-02-23 15:44 ` Daniel Gomez [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=hteidenzp7hrmblujwhvdgqkjxwumvgd5n3pc2otzggsibaak2@gzn6kraunmzf \
--to=da.gomez@samsung.com \
--cc=gost.dev@samsung.com \
--cc=kdevops@lists.linux.dev \
--cc=konstantin@linuxfoundation.org \
--cc=mcgrof@kernel.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 read-only IMAP folder(s) and NNTP newsgroup(s).