public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Mohan Boddu <mboddu@bhujji.com>
To: git-commits@fedoraproject.org
Subject: [rpms/fedora-repos] f45: Setup for rawhide being F37
Date: Mon, 10 Aug 2026 09:41:18 GMT	[thread overview]
Message-ID: <178635487899.1.5127833870288576794.rpms-fedora-repos-b7b688230c3b@fedoraproject.org> (raw)

            A new commit has been pushed.

            Repo   : rpms/fedora-repos
            Branch : f45
            Commit : b7b688230c3bdb51906ed4b45f1a2ee5d705dc3e
            Author : Mohan Boddu <mboddu@bhujji.com>
            Date   : 2022-02-08T16:18:27-05:00
            Stats  : +1/-0 in 1 file(s)
            URL    : https://src.fedoraproject.org/rpms/fedora-repos/c/b7b688230c3bdb51906ed4b45f1a2ee5d705dc3e?branch=f45

            Log:
            Setup for rawhide being F37

Adding F38 key

Signed-off-by: Mohan Boddu <mboddu@bhujji.com>

---
diff --git a/fedora-repos.spec b/fedora-repos.spec
index cf0671a..a75e3ed 100644
--- a/fedora-repos.spec
+++ b/fedora-repos.spec
@@ -77,6 +77,7 @@ Source54:       RPM-GPG-KEY-fedora-34-primary
 Source55:       RPM-GPG-KEY-fedora-35-primary
 Source56:       RPM-GPG-KEY-fedora-36-primary
 Source57:       RPM-GPG-KEY-fedora-37-primary
+Source58:       RPM-GPG-KEY-fedora-38-primary
 # When bumping Rawhide to fN, create N+1 key (and update archmap). (This
 # ensures users have the next future key installed and referenced, even if they
 # don't update very often. This will smooth out Rawhide N->N+1 transition for them).

             reply	other threads:[~2026-08-10  9:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-10  9:41 Mohan Boddu [this message]
2026-08-10  9:41 [rpms/fedora-repos] f45: Setup for rawhide being F37 Mohan Boddu
2026-08-10  9:41 Tomas Hrcka
2026-08-10  9:41 Mohan Boddu

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=178635487899.1.5127833870288576794.rpms-fedora-repos-b7b688230c3b@fedoraproject.org \
    --to=mboddu@bhujji.com \
    --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