public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Tomas Popela <tpopela@fedoraproject.org>
To: git-commits@fedoraproject.org
Subject: [flatpaks/flatpak-runtime] f45: Update README.md
Date: Fri, 11 Sep 2026 14:42:03 GMT [thread overview]
Message-ID: <178913772317.1.11937392591663336314.flatpaks-flatpak-runtime-7a0bba25c6dd@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : flatpaks/flatpak-runtime
Branch : f45
Commit : 7a0bba25c6dd06b51124edb49f1d6a6a9f21e45a
Author : Tomas Popela <tpopela@fedoraproject.org>
Date : 2022-06-13T12:19:42+00:00
Stats : +1/-1 in 1 file(s)
URL : https://src.fedoraproject.org/flatpaks/flatpak-runtime/c/7a0bba25c6dd06b51124edb49f1d6a6a9f21e45a?branch=f45
Log:
Update README.md
---
diff --git a/README.md b/README.md
index a51cdfd..5072dc5 100644
--- a/README.md
+++ b/README.md
@@ -85,7 +85,7 @@ Once done, please do the following steps in this exact order:
fetch-metadata` (replace f36 with the new release). You might need to update
the `/etc/fedmod/fedora.yaml` file and add a new release there. If the new
Fedora is already released, then duplicate the f36 part under the `releases:`
- section. If the new version isn't released yet, do the same, but replace
+ section [example](https://pagure.io/fork/tpopela/modularity/fedmod/c/0df9ced507b8e9ce76a62cc35015c403073873ca). If the new version isn't released yet, do the same, but replace
`fedora-stable` with `fedora-branched`.
7. Run `make new-runtime`. In case of any problems you will need to update the
`tools/resolve-files.py` to adapt it for new library versions and so on.
reply other threads:[~2026-09-11 14:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=178913772317.1.11937392591663336314.flatpaks-flatpak-runtime-7a0bba25c6dd@fedoraproject.org \
--to=tpopela@fedoraproject.org \
--cc=git-commits@fedoraproject.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