cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Andrew Price <anprice@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH] gfs2-utils: Update .gitignore for i18n files
Date: Thu, 04 Aug 2011 10:12:23 +0100	[thread overview]
Message-ID: <4E3A6277.7020808@redhat.com> (raw)
In-Reply-To: <20110803204052.GA865@andromeda.usersys.redhat.com>

On 03/08/11 21:40, Carlos Maiolino wrote:
> Maybe is a good idea to also add gfs2-utils.pot to this list. I believe we should
> remove gfs2-utils.pot from the upstream git repo, and leave it to be auto created
> at the compile time.
> Leaving this on the tree (and also into the package when it is created), make the
> gettext to bypass the creation of gfs2-utils.pot an rely on the one already created,
> which can be not up2date since we are doing some changes on strings and adding another
> things.
>
> What you guys think?

I think we need to keep gfs2-utils.pot in the git repo so that we have 
one single "master" translation template which should be used (by 
Transifex, translators, ...) to translate gfs2-utils.

When string changes occur (and once per release, minimum) we should 
regenerate the master gfs2-utils.pot and then merge those changes into 
the existing .po files and commit. That way we get full control over the 
current state of the single gfs2-utils.pot which is used by everyone.

Andy



  reply	other threads:[~2011-08-04  9:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-01 15:52 [Cluster-devel] [PATCH] gfs2-utils: Update .gitignore for i18n files Andrew Price
2011-08-01 16:03 ` Steven Whitehouse
2011-08-03 20:40 ` Carlos Maiolino
2011-08-04  9:12   ` Andrew Price [this message]
2011-08-04  9:26   ` 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=4E3A6277.7020808@redhat.com \
    --to=anprice@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).