public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Andrew Burgess <aburgess@redhat.com>
To: git-commits@fedoraproject.org
Subject: [rpms/gdb] fix-dup-patch: adjust commit message for gdb-backport-dap-core-file-support.patch
Date: Thu, 23 Jul 2026 18:36:34 GMT	[thread overview]
Message-ID: <178483179460.1.16975414453948481257.rpms-gdb-2a476679f1f2@fedoraproject.org> (raw)

            A new commit has been pushed.

            Repo   : rpms/gdb
            Branch : fix-dup-patch
            Commit : 2a476679f1f212901c32d53078ab4808127324bc
            Author : Andrew Burgess <aburgess@redhat.com>
            Date   : 2026-07-08T20:28:03+01:00
            Stats  : +10/-6 in 2 file(s)
            URL    : https://src.fedoraproject.org/rpms/gdb/c/2a476679f1f212901c32d53078ab4808127324bc?branch=fix-dup-patch

            Log:
            adjust commit message for gdb-backport-dap-core-file-support.patch

The commit message for patch gdb-backport-dap-core-file-support.patch
included lines that started with '---' which is a string also used
within diff markers.  This would confuse git when pushing the patches
to and from a git repository leading to this patch file constantly
showing up as changed.

This commit replaces '---' with '~~~' which has no special meaning for
git, and so avoids the confusion.

---
diff --git a/gdb-backport-dap-core-file-support.patch b/gdb-backport-dap-core-file-support.patch
index 7638031..d27f92b 100644
--- a/gdb-backport-dap-core-file-support.patch
+++ b/gdb-backport-dap-core-file-support.patch
@@ -18,7 +18,7 @@ within GDB's DAP protocol implementation:
 
 The commit messages for each individual commit follow:
 
---- 0a481bb9a6d:
+~~~ 0a481bb9a6d:
 
 gdb/dap: add support for opening core files
 
@@ -67,7 +67,7 @@ fail, I think we're OK.
 
 Approved-By: Tom Tromey <tom@tromey.com>
 
----  4ecaac39c26:
+~~~  4ecaac39c26:
 
 gdb/python: new events.corefile_changed event
 
@@ -90,7 +90,7 @@ and a single exited event.
 
 Reviewed-By: Eli Zaretskii <eliz@gnu.org>
 
---- ecac42af735:
+~~~ ecac42af735:
 
 Always propagate exceptions in DAP
 
@@ -104,7 +104,7 @@ done at the point of call.
 
 Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=33346
 
---- fc8e5a565b3:
+~~~ fc8e5a565b3:
 
 gdb: make structured core file mappings processing global
 
@@ -138,7 +138,7 @@ Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=32844
 
 Approved-By: Tom Tromey <tom@tromey.com>
 
---- f69c1d03c4d:
+~~~ f69c1d03c4d:
 
 gdb/python: add Corefile.mapped_files method
 
@@ -171,7 +171,7 @@ Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=32844
 
 Approved-By: Tom Tromey <tom@tromey.com>
 
---- 7862554bcf4:
+~~~ 7862554bcf4:
 
 gdb/python: introduce gdb.Corefile API
 

diff --git a/gdb.spec b/gdb.spec
index 72ca85e..ff754f6 100644
--- a/gdb.spec
+++ b/gdb.spec
@@ -928,6 +928,10 @@ fi
 # endif scl
 
 %changelog
+* Wed Jul 8 2026 Andrew Burgess <aburgess@redhat.com>
+- Adjust commit message in gdb-backport-dap-core-file-support.patch to
+  remove '---' string which confuses git.
+
 * Tue Jun 23 2026 Michal Kolar <mkolar@redhat.com> - 17.2-1
 - Rebase to FSF GDB 17.2.
   Deleted: gdb-rhbz2435950-skip-revert.patch

                 reply	other threads:[~2026-07-23 18:36 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=178483179460.1.16975414453948481257.rpms-gdb-2a476679f1f2@fedoraproject.org \
    --to=aburgess@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