git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Frank Li <lznuaa@gmail.com>
To: git@vger.kernel.org,
	tortoisegit-dev <tortoisegit-dev@googlegroups.com>,
	tortoisegit-users@googlegroups.com,
	tortoisegit-announce@googlegroups.com
Subject: [ANNOUNCE] for TortoiseGit 1.2.1.0
Date: Mon, 16 Nov 2009 22:17:16 -0600	[thread overview]
Message-ID: <1976ea660911162017v4fcdcf01l92dda17da622258a@mail.gmail.com> (raw)

http://tortoisegit.googlecode.com/files/TortoiseGit-1.2.1.0-32bit.msi
http://tortoisegit.googlecode.com/files/TortoiseGit-1.2.1.0-64bit.msi

= Release 1.2.1.0 =
== Features ==
 * Add color success and fail at ProgressDlg

 * Log Dialog
  Show work copy to log dialog. User can commit change at log dialog.
  Easy to compare with working copy difference

 * Allow Alt+O in commit dialog for OK

 * Sync Dialog remote URL support save history

 * Add remote branch and current branch at proptery page

 * Add no-commit option at merge dialog

 * Enable IBugTraqProvide CheckCommit and OnCommitFinished

== Bug Fix ==
 * Fixed issue #219: Blame Error when git repository is at root
directory and path use "/"
 * Fixed issue #214: installer inserts unused or faulty registry key
 * Fixed issue #179: Log dialog lacks information about changed files
 * Fixed issue #209: High CPU usage in tortoiseproc.exe & limit line number
 * Fixed issue #212: Disable the "Select items automaticlly" option
has no effect to commit files dialog
 * Fixed issue #209: High CPU usage in tortoiseproc.exe & Append text
to edit ctrl
 * Fixed Issue #203:  Remote URL select box in sync dialog is not
populated with remotes.
 * Fixed Issue #208:  During push (from context menu), branches
missing from drop down list.
 * Fixed issue #86: Globally sets HOME affecting third-party
applications (GNU Emacs)
 * Fixed issue #188: Add Git Properties tab into Windows File Properties

                 reply	other threads:[~2009-11-17  4:17 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=1976ea660911162017v4fcdcf01l92dda17da622258a@mail.gmail.com \
    --to=lznuaa@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=tortoisegit-announce@googlegroups.com \
    --cc=tortoisegit-dev@googlegroups.com \
    --cc=tortoisegit-users@googlegroups.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).