public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Joseph S. Myers" <joseph@codesourcery.com>
To: gcc-patches@gcc.gnu.org
Subject: Re: New template for 'gcc' made available
Date: Wed, 10 Oct 2007 13:22:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.64.0710101321390.871@digraph.polyomino.org.uk> (raw)
In-Reply-To: <E1IfOQS-0001j3-DL@neoduik.vrijschrift.org>

I've committed the new merged .po files for gcc and cpplib to trunk and 
4.2 branch.

-- 
Joseph S. Myers
joseph@codesourcery.com

  reply	other threads:[~2007-10-10 13:22 UTC|newest]

Thread overview: 61+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-09 23:23 Translation Project Robot
2007-10-10 13:22 ` Joseph S. Myers [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-05-09  9:22 Translation Project Robot
2024-02-19 16:37 Translation Project Robot
2023-07-28 10:06 Translation Project Robot
2023-04-27  7:15 Translation Project Robot
2023-04-12  7:53 Translation Project Robot
2023-02-22 10:26 Translation Project Robot
2022-08-23 15:50 Translation Project Robot
2022-05-08  9:36 Translation Project Robot
2022-04-05  9:53 Translation Project Robot
2022-02-15  9:00 Translation Project Robot
2021-04-28  9:49 Translation Project Robot
2021-03-23 11:15 Translation Project Robot
2021-02-09 11:24 Translation Project Robot
2020-07-23 17:34 Translation Project Robot
2020-05-08  7:37 Translation Project Robot
2020-03-24 10:03 Translation Project Robot
2020-02-10 19:23 Translation Project Robot
2019-05-07 17:25 Translation Project Robot
2019-04-15  9:07 Translation Project Robot
2019-03-25 20:22 Translation Project Robot
2019-02-05 18:33 Translation Project Robot
2018-07-26 18:59 Translation Project Robot
2018-05-03  7:46 Translation Project Robot
2018-04-04  8:12 Translation Project Robot
2018-04-02 14:39 Translation Project Robot
2018-04-03 20:12 ` Joseph Myers
2018-01-29 20:36 Translation Project Robot
2017-08-14 20:45 Translation Project Robot
2017-05-02 16:22 Translation Project Robot
2017-04-28 12:18 Translation Project Robot
2017-02-27 16:14 Translation Project Robot
2017-01-03 12:07 Translation Project Robot
2016-08-24  9:46 Translation Project Robot
2016-04-27 14:03 Translation Project Robot
2016-02-02 20:23 Translation Project Robot
2015-07-21 18:33 Translation Project Robot
2015-04-29  8:02 Translation Project Robot
2015-02-09 21:11 Translation Project Robot
2014-02-03 10:21 Translation Project Robot
2013-03-27 11:00 Translation Project Robot
2013-02-26 20:57 Translation Project Robot
2012-09-24 19:01 Translation Project Robot
2012-06-22 18:17 Translation Project Robot
2012-06-22 17:59 Translation Project Robot
2012-03-25 10:09 Translation Project Robot
2012-01-29 16:46 Translation Project Robot
2011-07-08 16:29 Translation Project Robot
2011-04-03  7:45 Translation Project Robot
2010-12-20  1:44 Translation Project Robot
2010-11-14 22:02 Translation Project Robot
2010-11-03 19:01 Translation Project Robot
2010-04-16  6:28 Translation Project Robot
2010-02-05  9:29 Translation Project Robot
2009-12-04 10:04 Translation Project Robot
2009-07-23 17:41 Translation Project Robot
2008-11-25 13:30 Translation Project Robot
2008-03-14  0:56 Translation Project Robot
2007-11-10 16:57 Translation Project Robot
2007-08-14 22:40 Translation Project Robot

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=Pine.LNX.4.64.0710101321390.871@digraph.polyomino.org.uk \
    --to=joseph@codesourcery.com \
    --cc=gcc-patches@gcc.gnu.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).