git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Shawn O. Pearce" <spearce@spearce.org>
To: git@vger.kernel.org
Subject: git-gui 0.9.1 release plans
Date: Mon, 24 Dec 2007 23:54:41 -0500	[thread overview]
Message-ID: <20071225045441.GQ14735@spearce.org> (raw)

So git-gui 0.9.1...

I have 12 changes in `master` since 0.9.0 that will be included.
Other than these changes, and maybe Bernt's "always append LF in
commit message" patch, this is what will make up the 0.9.1 release.

I expect 0.9.1 will be the last git-gui release before git 1.5.4
goes final, which means git 1.5.4 will be shipping with 0.9.1.

Translators, testers, etc. please speak up in the next week and a
half and get your patches in if there are any outstanding translation
changes or minor bug fixes that should be included.


I'm on vacation (and completely offline) Jan. 5-13th, so I'd like
to wrap up 0.9.1 by the 4th if I can, as Junio has been targeting
for a mid-Jan release of git 1.5.4.


---  Changes since 0.9.0 ---

Christian Stimming (2):
      Update git-gui.pot with latest (few) string additions and changes.
      Update German translation. 100% completed.

Johannes Sixt (2):
      git-gui: Improve the application icon on Windows.
      git-gui: Move frequently used commands to the top of the context menu.

Mark Levedahl (1):
      git-gui: Unconditionally use absolute paths with Cygwin

Michele Ballabio (2):
      git-gui: fix a typo in lib/commit.tcl
      git-gui: update it.po and glossary/it.po

Miklos Vajna (1):
      Update Hungarian translation. 100% completed.

Robert Schiele (1):
      git-gui: install-sh from automake does not like -m755

Shawn O. Pearce (1):
      git-gui: Handle file mode changes (644->755) in diff viewer

brian m. carlson (1):
      git-gui: Reorder msgfmt command-line arguments

しらいしななこ (1):
      Update ja.po for git-gui


-- 
Shawn.

                 reply	other threads:[~2007-12-25  4:55 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20071225045441.GQ14735@spearce.org \
    --to=spearce@spearce.org \
    --cc=git@vger.kernel.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 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).