From: "Marco Costalba" <mcostalba@gmail.com>
To: git@vger.kernel.org
Cc: proski@gnu.org
Subject: [ANNOUNCE] qgit 1.1
Date: Sat, 18 Feb 2006 14:14:42 +0100 [thread overview]
Message-ID: <e5bfff550602180514p2ef6eefodb6112cb3b32041f@mail.gmail.com> (raw)
This is qgit-1.1
With qgit you will be able to browse revisions history, view patch
content and changed
files, graphically following different development branches.
FEATURES
- View revisions, diffs, files history, files annotation, archive tree.
- Commit changes visually cherry picking modified files.
- Apply or format patch series from selected commits, drag and
drop commits between two instances of qgit.
- qgit implements a GUI for the most common StGIT commands like push/pop
and apply/format patches. You can also create new patches or refresh
current top one using the same semantics of git commit, i.e. cherry picking
single modified files.
NEW IN THIS RELEASE
A lot of work has been done by Pavel and me from 1.0, too much to list.
A notably change from the last rc3 is a much improved GUI, courtesy of Pavel,
and various stability fixes.
Update to 1.1 is suggested for all users.
Please note that you will need git 1.2 or newer.
DOWNLOAD
SourceForge tarball link is:
http://prdownloads.sourceforge.net/qgit/qgit-1.1.tar.bz2?download
Refer to http://digilander.libero.it/mcostalba/ for additional links
and detailed change log.
Installation should be as simple as ./configure + make + make install-strip
The last one (install-strip) to have a much smaller bin with debug
info stripped.
Please refer to shipped README file for more information.
In case you prefer to clone from the public git repository:
http://digilander.libero.it/mcostalba/scm/qgit.git
you may run 'autoreconf -i' before ./configure
Marco
reply other threads:[~2006-02-18 13:14 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=e5bfff550602180514p2ef6eefodb6112cb3b32041f@mail.gmail.com \
--to=mcostalba@gmail.com \
--cc=git@vger.kernel.org \
--cc=proski@gnu.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).