From: David <davvid@gmail.com>
To: git@vger.kernel.org
Subject: [ANNOUNCE] ugit: the pythonic git gui
Date: Fri, 28 Dec 2007 14:49:18 -0800 [thread overview]
Message-ID: <402731c90712281449g3d0c4f53w48c65dc8883bbbb3@mail.gmail.com> (raw)
ugit, the pyqt-based git gui, has been taking shape as of late.
First off, I'd like to thank everyone that replied with suggestions
and criticism. This list is extremely helpful with regards to
providing honest software critiques.
New features since the last announcement (almost all of which were
mentioned in one way or another on this list):
* inotify support (we've removed the "Rescan" button)
* Patch hunk un/staging
* Allows un/staging selected patch hunk lines (without --unidiff-zero)
* Prepped for i18n ("env LANG=ja_JP ugit" looks pretty cool now)
* I'm a westerner, so the unstaged list is now on the left and the
staged list is on the right (thanks Jason)
* Optimizations to improve the interactivity of the patch browser
* Misc. fixes for MacOS and Windows (thanks Steffan and Sebastian)
* Uses default system colors whenever possible [no more darkness] (thanks Alex)
* No longer requires PYTHONPATH
Source code (requires pyqt4-dev-tools to build):
http://repo.or.cz/w/ugit.git
Tarballs (require a stock pyqt-4.3 installation):
http://ugit.justroots.com/
I'll try and get some .deb, .rpm, etc. action happening soon.
p.s.
If you read ugit as "(f)uh-git" or "ugly-git", then that's good since
I think that falls in line with the git style ;-)
next reply other threads:[~2007-12-28 22:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-28 22:49 David [this message]
2008-01-02 10:42 ` [ANNOUNCE] ugit: the pythonic git gui Guilhem Bonnefille
2008-01-03 3:20 ` David
2008-01-04 7:15 ` Marco Costalba
2008-01-04 9:05 ` Abdelrazak Younes
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=402731c90712281449g3d0c4f53w48c65dc8883bbbb3@mail.gmail.com \
--to=davvid@gmail.com \
--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).