From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH] gfs2-utils: Update .gitignore for i18n files
Date: Thu, 04 Aug 2011 10:26:48 +0100 [thread overview]
Message-ID: <1312450008.2712.24.camel@menhir> (raw)
In-Reply-To: <20110803204052.GA865@andromeda.usersys.redhat.com>
Hi,
On Wed, 2011-08-03 at 17:40 -0300, Carlos Maiolino wrote:
> On Mon, Aug 01, 2011 at 04:52:09PM +0100, Andrew Price wrote:
> > Add entries in .gitignore for some i18n-related files which are
> > generated at build time.
> >
> > Signed-off-by: Andrew Price <anprice@redhat.com>
> > ---
> > .gitignore | 4 ++++
> > 1 files changed, 4 insertions(+), 0 deletions(-)
> >
> > diff --git a/.gitignore b/.gitignore
> > index 62e4ac6..e8b7ea1 100644
> > --- a/.gitignore
> > +++ b/.gitignore
> > @@ -37,3 +37,7 @@ gfs2/tool/gfs2_tool
> > gfs2/tune/tunegfs2
> > group/gfs_control/gfs_control
> > group/gfs_controld/gfs_controld
> > +ABOUT-NLS
> > +po/Makevars.template
> > +po/POTFILES
> > +po/stamp-po
> > --
> > 1.7.6
> >
>
> 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?
>
Do we need to have a .pot in the tree for transifex to use as the basis
for new translations? If not, then lets create it at build time,
otherwise I think we have no choice but to leave it in the tree and to
remember to recreate it when the strings have changed,
Steve.
prev parent reply other threads:[~2011-08-04 9:26 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
2011-08-04 9:26 ` Steven Whitehouse [this message]
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=1312450008.2712.24.camel@menhir \
--to=swhiteho@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).