From: "Frank Li" <lznuaa@gmail.com>
To: git@vger.kernel.org, tortoisegit-announce@googlegroups.com
Subject: announce: TortoiseGit 0.2 preview released
Date: Sun, 4 Jan 2009 23:15:19 +0800 [thread overview]
Message-ID: <1976ea660901040715l36667c7dld5f686e8c3624d1b@mail.gmail.com> (raw)
After heavy developing, TortoiseGit 0.2 preview release published.
TortoiseGit 0.2 can finish regular work, such as commit, show log,
diff version, create tag, create branch, create patchs.
Download:
http://code.google.com/p/tortoisegit/downloads/list
Version 0.2.0.0 preview version:
Features:
1. Add TortoisgeMerge as default compare tools
2. Pull, Fetch, Push
3. Create Branch\Tag
4. Switch branch \Chechout
5. Compare with previous version
6. Clone(only support local repository, see known issue for detail)
7. Log Dialog support filter
8. Check for modifications
9. Revert local change
10.Create Patch Serial
11.Apply Patch Serial
12.Add file to repository(see know issue)
13.Export to zip file
Bug Fix:
1. A2W cause stack overwrite bug when git output is long.
Known Issue:
1. ProcessDlg will wait for ever when clone remote repository(ssh, http,git).
2. push fetch and pull don't support password mode. Just support
public key problem.
3. Just fetch first 100 log item.
4. If install TortoiseGit before MsysGit, you need modify register
HKEY_LOCAL_MACHINE\Software\TortoiseGit\\MsysGit\
Let it point to correct msysgit install path.
5. Add File, please commit and show unversion file, the choose add
file, then right clict, Choose Add file
6. To new initial repository, You will not see add file again in
commit dialog box if give up commit when choose add
next reply other threads:[~2009-01-04 15:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-04 15:15 Frank Li [this message]
2009-01-05 6:40 ` announce: TortoiseGit 0.2 preview released Ping Yin
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=1976ea660901040715l36667c7dld5f686e8c3624d1b@mail.gmail.com \
--to=lznuaa@gmail.com \
--cc=git@vger.kernel.org \
--cc=tortoisegit-announce@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).