public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Jan Grulich <jgrulich@redhat.com>
To: git-commits@fedoraproject.org
Subject: [rpms/glib2] cve-2026-58016-f44: Packit: drop fast_forward_merge_into as current stable branches diverge
Date: Tue, 11 Aug 2026 10:38:39 GMT	[thread overview]
Message-ID: <178644471999.1.2789551138695188160.rpms-glib2-6099fd5fb673@fedoraproject.org> (raw)

A new commit has been pushed.

Repo   : rpms/glib2
Branch : cve-2026-58016-f44
Commit : 6099fd5fb67388b71517693f24baf2833acef661
Author : Jan Grulich <jgrulich@redhat.com>
Date   : 2026-02-25T12:57:56+01:00
Stats  : +1/-7 in 1 file(s)
URL    : https://src.fedoraproject.org/rpms/glib2/c/6099fd5fb67388b71517693f24baf2833acef661?branch=cve-2026-58016-f44

Log:
Packit: drop fast_forward_merge_into as current stable branches diverge

---
diff --git a/.packit.yaml b/.packit.yaml
index b8fe31c..93c7e86 100644
--- a/.packit.yaml
+++ b/.packit.yaml
@@ -12,14 +12,8 @@ jobs:
   # Automated updates for stable branches
   - job: pull_from_upstream
     trigger: release
-    # Packit does the full update (spec, changelog) on the latest stable branch.
-    # The exact same commit is reused to open PRs for all other stable branches,
-    # which can be merged with fast-forward only (git merge --ff-only),
-    # keeping a linear, non-divergent history across branches.
     dist_git_branches:
-      fedora-latest-stable:
-        fast_forward_merge_into:
-          - fedora-stable
+      - fedora-stable
 
     # ========================================================================
     # VERSIONING: Choose ONE option based on your package's versioning scheme

                 reply	other threads:[~2026-08-11 10:38 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=178644471999.1.2789551138695188160.rpms-glib2-6099fd5fb673@fedoraproject.org \
    --to=jgrulich@redhat.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