From: Daniel Gomez <da.gomez@samsung.com>
To: "kdevops@lists.linux.dev" <kdevops@lists.linux.dev>,
"mcgrof@kernel.org" <mcgrof@kernel.org>
Cc: "gost.dev@samsung.com" <gost.dev@samsung.com>,
Daniel Gomez <da.gomez@samsung.com>
Subject: [PATCH v2 0/1] linux: generate refs automatically
Date: Fri, 16 Feb 2024 09:18:28 +0000 [thread overview]
Message-ID: <20240216091828.133753-1-da.gomez@samsung.com> (raw)
In-Reply-To: CGME20240216091829eucas1p176479ddf791b339a27aea814a553b5ff@eucas1p1.samsung.com
Add support to generate git references automatically using git-ls-remote.
Changes since v1:
* Script generation moved and called from the main Makefile.
* scripts/gen-refs.Makefile to generate refs.
* Conversion to python.
* Added support for:
* Command-line arguments to control options.
* YAML parser to configure extra and static references. Example added for mcgrof and mcgrof-next.
* Filter for tags and heads. Example to filter semantic versioning would be --filter-tags "*.*.*".
* File generation based on time. Update it every 24h (hardcoded). Possibility to
use --force to always generate the file.
* git-ls-remote sorting inverted using --sort option and git versionsort.suffix
option (to avoid sort --reverse).
Note: Examples for static/extra configs are only applied for mcgrof's dev trees.
I can also add support for the other trees (jlayton, cel...). Let me know if you
want to give this a try for these trees also.
Daniel
Daniel Gomez (1):
linux: generate refs automatically
.gitignore | 2 +
Makefile | 1 +
scripts/gen-refs.Makefile | 48 +++++
scripts/generate_refs.py | 242 ++++++++++++++++++++++++++
workflows/linux/Kconfig | 8 +-
workflows/linux/Kconfig.linus | 39 +----
workflows/linux/Kconfig.mcgrof | 42 +----
workflows/linux/Kconfig.next | 4 +-
workflows/linux/Kconfig.stable | 51 +-----
workflows/linux/mcgrof-next-refs.yaml | 10 ++
workflows/linux/mcgrof-refs.yaml | 10 ++
11 files changed, 322 insertions(+), 135 deletions(-)
create mode 100644 scripts/gen-refs.Makefile
create mode 100755 scripts/generate_refs.py
create mode 100644 workflows/linux/mcgrof-next-refs.yaml
create mode 100644 workflows/linux/mcgrof-refs.yaml
--
2.43.0
next parent reply other threads:[~2024-02-16 9:18 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 ` Daniel Gomez [this message]
[not found] ` <CGME20240216091830eucas1p1e5ee4b905b2977e2b7de54b9f4be222b@eucas1p1.samsung.com>
2024-02-16 9:18 ` [PATCH v2 1/1] linux: generate refs automatically 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
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=20240216091828.133753-1-da.gomez@samsung.com \
--to=da.gomez@samsung.com \
--cc=gost.dev@samsung.com \
--cc=kdevops@lists.linux.dev \
--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).