From: Jeff Law <jeffreyalaw@gmail.com>
To: binutils@sourceware.org
Subject: Re: [PATCH] Pass PKG_CONFIG_PATH down from top-level Makefile
Date: Thu, 13 Oct 2022 19:31:09 -0600 [thread overview]
Message-ID: <65995e54-9fb6-8ecc-dc86-131b199652b5@gmail.com> (raw)
In-Reply-To: <71a243a9-9afb-caac-6bef-85ea6ab82ec7@simark.ca>
On 10/11/22 21:08, Simon Marchi via Binutils wrote:
> Hi gcc-patches,
>
> I had applied the patch below to binutils-gdb, but it recently got wiped
> out by a gcc -> binutils-gdb configure.ac sync. Would it be possible to
> apply it to the gcc repo so this doesn't happen again?
Better yet, let's get you access to the GCC repo so that you can install
approved bits yourself :-) It's a lot easier for someone to say OK than
to extract the patch, apply it & push it.
Given you've got access to binutils-gdb, I think it's just a matter of
putting you into the gcc group.
https://gcc.gnu.org/gitwrite.html#authenticated
Should have a link to the magic form.
jeff
prev parent reply other threads:[~2022-10-14 1:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-15 21:26 Simon Marchi
2022-03-29 20:04 ` Simon Marchi
2022-04-07 19:09 ` Simon Marchi
2022-04-08 14:32 ` Nick Clifton
2022-04-08 14:57 ` Simon Marchi
2022-10-12 3:08 ` Simon Marchi
2022-10-14 1:31 ` Jeff Law [this message]
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=65995e54-9fb6-8ecc-dc86-131b199652b5@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=binutils@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).