cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Carlos Maiolino <cmaiolino@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH] Track translatable files
Date: Tue, 14 Jun 2011 11:24:41 -0300	[thread overview]
Message-ID: <1308061481-5838-1-git-send-email-cmaiolino@redhat.com> (raw)

This is the first patch adding the possible
translatable files to the i18n infra-structure.
This is the list of files which will be monitored
by the i18n and set to have translatable strings

Please discard the previous patch, once it has
obsolete files into the tracking list
---
 po/POTFILES.in |   36 ++++++++++++++++++++++++++++++++++++
 1 files changed, 36 insertions(+), 0 deletions(-)

diff --git a/po/POTFILES.in b/po/POTFILES.in
index 667e27c..88d2198 100644
--- a/po/POTFILES.in
+++ b/po/POTFILES.in
@@ -1 +1,37 @@
 # List of source files which contain translatable strings.
+#
+#edit tool
+gfs2/edit/extended.c
+gfs2/edit/gfs2hex.c
+gfs2/edit/hexedit.c
+gfs2/edit/savemeta.c
+
+#fsck tool
+gfs2/fsck/eattr.c
+gfs2/fsck/fs_recovery.c
+gfs2/fsck/hash.c
+gfs2/fsck/initialize.c
+gfs2/fsck/inode_hash.c
+gfs2/fsck/link.c
+gfs2/fsck/lost_n_found.c
+gfs2/fsck/main.c
+gfs2/fsck/metawalk.c
+gfs2/fsck/pass1b.c
+gfs2/fsck/pass1.c
+gfs2/fsck/pass1c.c
+gfs2/fsck/pass2.c
+gfs2/fsck/pass3.c
+gfs2/fsck/pass4.c
+gfs2/fsck/pass5.c
+gfs2/fsck/rgrepair.c
+gfs2/fsck/util.c
+
+#mkfs tool
+gfs2/mkfs/main.c
+gfs2/mkfs/main_grow.c
+gfs2/mkfs/main_jadd.c
+gfs2/mkfs/main_mkfs.c
+
+#tune tool
+gfs2/tune/main.c
+gfs2/tune/super.c
-- 
1.7.5.2



             reply	other threads:[~2011-06-14 14:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-14 14:24 Carlos Maiolino [this message]
2011-06-14 14:31 ` [Cluster-devel] [PATCH] Track translatable files Steven Whitehouse
  -- strict thread matches above, loose matches on Subject: below --
2011-06-14 13:50 Carlos Maiolino
2011-06-14 13:58 ` Steven Whitehouse
2011-06-14 14:03   ` Carlos Maiolino
2011-06-14 14:09     ` Steven Whitehouse

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=1308061481-5838-1-git-send-email-cmaiolino@redhat.com \
    --to=cmaiolino@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;
as well as URLs for NNTP newsgroup(s).