From: Carles Pina i Estany <carles@pina.cat>
To: grub-devel@gnu.org
Subject: Re: merging of gettext branch
Date: Sat, 21 Nov 2009 21:33:42 +0000 [thread overview]
Message-ID: <20091121213342.GA25774@pina.cat> (raw)
In-Reply-To: <20091121212712.GA25254@pina.cat>
Hi,
On Nov/21/2009, Carles Pina i Estany wrote:
> My gettext branch:
> bzr.savannah.gnu.org/srv/bzr/grub/people/cpina/gettext/
If the branch wants to be merged I suggest to use this ChangeLog:
--------
YYYY-MM-DD Carles Pina i Estany <carles@pina.cat>
* conf/common.rmk: Add grub-gettext_lib target, dependency and
SOURCES, CFLAGS, LDFLAGS
* gettext/gettext.c: New file with gettext implementation
* include/grub/i18n_grub.h: New file with grub_gettext macros
* include/grub/misc.h: Define macro _(char *s). Declare
grub_gettext_dummy and grub_gettext
* kern/misc.c: Define grub_gettext symbol implementation of the
grub_gettext_dummy function
* normal/menu_text.c: Gettextize one message in print_message
* po/POTFILES: Adds normal/menu_text.c
* po/ca.po: Adds the new string
* util/grub.d/00_header.in: defines gettext variables and loads
the module
--------
Since the commits of the branch doesn't follow the rules correctly
--
Carles Pina i Estany
http://pinux.info
next prev parent reply other threads:[~2009-11-21 21:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-21 21:27 merging of gettext branch Carles Pina i Estany
2009-11-21 21:33 ` Carles Pina i Estany [this message]
2009-11-21 22:00 ` Robert Millan
2009-11-21 22:14 ` Carles Pina i Estany
2009-11-21 23:09 ` Robert Millan
2009-11-21 23:18 ` Vladimir 'φ-coder/phcoder' Serbinenko
2009-11-21 23:40 ` Robert Millan
2009-11-22 12:47 ` Carles Pina i Estany
2009-11-22 12:46 ` Carles Pina i Estany
2009-11-22 17:07 ` Carles Pina i Estany
2009-11-22 18:45 ` Carles Pina i Estany
2009-11-22 21:26 ` Robert Millan
2009-11-22 22:27 ` Carles Pina i Estany
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=20091121213342.GA25774@pina.cat \
--to=carles@pina.cat \
--cc=grub-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.