From: Eli Zaretskii <eliz@gnu.org>
To: tromey@redhat.com
Cc: gdb-patches@sourceware.org
Subject: Re: FYI: use UTF-16 and UTF-32, not UCS-2 and UCS-4
Date: Sat, 26 Sep 2009 09:02:00 -0000 [thread overview]
Message-ID: <837hvmt6tr.fsf@gnu.org> (raw)
In-Reply-To: <m363b6yczm.fsf@fleche.redhat.com>
> From: Tom Tromey <tromey@redhat.com>
> Date: Fri, 25 Sep 2009 14:40:29 -0600
>
> I am undecided as to whether I ought to push this into the 7.0 branch.
> Any opinions?
I'd prefer that the branch commits be limited to clear bugfixs only,
at this time.
next prev parent reply other threads:[~2009-09-26 9:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-25 20:40 Tom Tromey
2009-09-26 9:02 ` Eli Zaretskii [this message]
2009-09-26 11:56 ` Pierre Muller
2009-09-26 13:12 ` Eli Zaretskii
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=837hvmt6tr.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=tromey@redhat.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