git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Shawn O. Pearce" <spearce@spearce.org>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
	Christian Stimming <stimming@tuhh.de>,
	git@vger.kernel.org
Subject: git-gui i18n status?
Date: Sat, 1 Sep 2007 00:29:24 -0400	[thread overview]
Message-ID: <20070901042924.GE18160@spearce.org> (raw)

Now that git-gui 0.8.2 is out and git 1.5.3 is just around the corner
I am starting to think about bringing the git-gui i18n work into the
main git-gui tree, so we can start working from a common codebase.

Looking at the repository on repo.or.cz it looks like it needs to
be merged/rebased onto 0.8.2.  There is a trivial merge conflict,
but there are some more subtle ones caused by the movement of
the library directory initialization down lower in git-gui.sh.
For example translations won't be initialized if we have an issue
with the output of git-version and want to prompt the user.

What is the current plan?  Should I be looking at the master branch
of git://repo.or.cz/git-gui/git-gui-i18n.git for pulling?  Or are
folks expecting that this series will be cleaned up before I pull it?

-- 
Shawn.

             reply	other threads:[~2007-09-01  4:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-01  4:29 Shawn O. Pearce [this message]
2007-09-01 23:42 ` git-gui i18n status? Johannes Schindelin
2007-09-02  1:00   ` Junio C Hamano
2007-09-02  1:42   ` Shawn O. Pearce
2007-09-02  2:24     ` Shawn O. Pearce
2007-09-02 12:20       ` Johannes Schindelin
2007-09-16 12:03         ` Christian Stimming
2007-09-17  3:20           ` Shawn O. Pearce
2007-09-17  9:04             ` Johannes Schindelin
2007-09-02 12:29     ` Johannes Schindelin
2007-09-02 14:17   ` Michele Ballabio
  -- strict thread matches above, loose matches on Subject: below --
2007-09-02 15:09 Michele Ballabio

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070901042924.GE18160@spearce.org \
    --to=spearce@spearce.org \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=stimming@tuhh.de \
    /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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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).