public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/toolchain/binutils-patches:master commit in: /
Date: Mon, 12 Aug 2024 13:40:44 +0000 (UTC)	[thread overview]
Message-ID: <1723470041.bc078d7a8f62243194491cfe4c858ed49fd9fe6c.sam@gentoo> (raw)

commit:     bc078d7a8f62243194491cfe4c858ed49fd9fe6c
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Mon Aug 12 13:40:33 2024 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Mon Aug 12 13:40:41 2024 +0000
URL:        https://gitweb.gentoo.org/proj/toolchain/binutils-patches.git/commit/?id=bc078d7a

README.Gentoo.patches: fix typo

Signed-off-by: Sam James <sam <AT> gentoo.org>

 README.Gentoo.patches | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.Gentoo.patches b/README.Gentoo.patches
index f888dbf..e183a61 100644
--- a/README.Gentoo.patches
+++ b/README.Gentoo.patches
@@ -3,7 +3,7 @@
  ============
 
 Gentoo patchsets for binutils are maintained as vendor branches of the upstream
-binutils-glb git repository. From there, we bundle all the commits into a tarball
+binutils-gdb git repository. From there, we bundle all the commits into a tarball
 and distribute it via our public mirroring system.
 
 If you want specific info about a patch (like what it does or whose great idea 


             reply	other threads:[~2024-08-12 13:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-12 13:40 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-08-17 22:04 [gentoo-commits] proj/toolchain/binutils-patches:master commit in: / Andreas K. Hüttel
2021-08-17 20:47 Andreas K. Hüttel
2020-07-25 11:08 Andreas K. Hüttel
2020-07-25 11:08 Andreas K. Hüttel

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=1723470041.bc078d7a8f62243194491cfe4c858ed49fd9fe6c.sam@gentoo \
    --to=sam@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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