public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Nick Clifton <nickc@redhat.com>
To: "Arsen Arsenović" <arsen@aarsen.me>
Cc: Jan Beulich <jbeulich@suse.com>, Bruno Haible <bruno@clisp.org>,
	Iain Sandoe <iain@sandoe.co.uk>,
	gdb-patches@sourceware.org, binutils@sourceware.org
Subject: Re: [PATCH v2 1/2] *: add modern gettext support
Date: Thu, 28 Sep 2023 10:43:26 +0100	[thread overview]
Message-ID: <58600bef-a9ec-b2c7-e7a2-f33c72da29f2@redhat.com> (raw)
In-Reply-To: <86y1grmrty.fsf@aarsen.me>

Hi Arsen,

> Thanks for the review.  I don't have push rights in binutils-gdb.git, so
> I'll send you a patchset with an updated commit message (see
> https://inbox.sourceware.org/864jjhrm73.fsf@aarsen.me/) off-list when
> this patchset is reviewed on the GCC side also, so that you can push it.

That works for me.

Cheers
   Nick



  reply	other threads:[~2023-09-28  9:43 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-26  0:17 [PATCH v2 0/2] Replace intl/ with out-of-tree GNU gettext Arsen Arsenović
2023-09-26  0:17 ` [PATCH v2 1/2] *: add modern gettext support Arsen Arsenović
2023-09-26  2:12   ` Kevin Buettner
2023-09-26  7:03   ` Jan Beulich
2023-09-26  7:54     ` Iain Sandoe
2023-09-26 14:44     ` Arsen Arsenović
2023-09-27  7:11       ` Jan Beulich
2023-09-27 13:06         ` Arsen Arsenović
2023-09-27 15:19         ` Nick Clifton
2023-09-27 17:43           ` Arsen Arsenović
2023-09-28  9:43             ` Nick Clifton [this message]
2023-09-29 15:58       ` Bruno Haible
2023-09-29 16:27         ` Arsen Arsenović
2023-11-20 16:42   ` Kévin Le Gouguec
2023-11-20 20:30     ` Arsen Arsenović
2023-11-20 21:28       ` Bruno Haible
2023-09-26  0:17 ` [PATCH v2 2/2] *: suppress xgettext 0.22 charset name error Arsen Arsenović
2023-09-27 15:21   ` Nick Clifton

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=58600bef-a9ec-b2c7-e7a2-f33c72da29f2@redhat.com \
    --to=nickc@redhat.com \
    --cc=arsen@aarsen.me \
    --cc=binutils@sourceware.org \
    --cc=bruno@clisp.org \
    --cc=gdb-patches@sourceware.org \
    --cc=iain@sandoe.co.uk \
    --cc=jbeulich@suse.com \
    /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).