[ANNOUNCE] qgit-2.0

This is the final qgit-2.0

With qgit you will be able to browse revision histories, view patch content
and changed files, graphically following different development branches.


IMPORTANT NOTE
git 1.5.3 or better is required, Qt 4.3 or better is required.


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.

- Associate commands sequences, scripts and anything else executable
to a custom action. Actions can be run from menu and corresponding
output is grabbed by a terminal window.

- 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

This is the final public release of the shining new qgit 2.0 based on
the shining new Qt 4.3 libraries.

All the features of the stable series have been ported. In addition this
new release sports a better GUI both on visually side and on usability side.

Annotation code is much improved in speed and in power, as example
now follows file renames, try it on any git tree file to see a real example.

A new and much improved repository browsing experience is now possible,
in particular you don't need to switch to patch tab to view diff
content anymore. Patch information, together with patch description,
is shown in bottom left pane.

Finally, qgit works natively under Windows due to Qt 4.3 libraries.


The detailed list of changes is very long and interested people can
read from public qgit repository.

Although there are a lot of new features code is considered stable due
to have been very long in 'rc' state.


You can download the tarball from
http://sourceforge.net/projects/qgit

or clone the public git repository at
git://git.kernel.org/pub/scm/qgit/qgit4.git


Please, check the shipped README for detailed build and install information.


Have fun
Marco
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Relevant Pages

  • Re: Linux 2.6.16-rc1
    ... if you want to judge how big a patch is by the number of files it ... that it is a real measure of how likely a commit was to impact other ... some of which are very core (the TTY layer buffering revamp), ... a word of warning - git is efficient, but doing things like the above ...
    (Linux-Kernel)
  • Re: [PATCH] [1/2many] - FInd the maintainer(s) for a patch - scripts/get_maintainer.pl
    ... MAINTAINERS information, we have 3 options: ... There are things git can help, and other things git does not ... Linus already gave a script to grep *-by: lines from commit ... integration to git-based patch flow. ...
    (Linux-Kernel)
  • Re: 2.6.18-mm1
    ... then I come to commit it: ... Think of it as "diffstat for git". ... (otherwise you would somehow need to parse the patch and find ... If you _are_ updating index yourself before calling git-commit, ...
    (Linux-Kernel)
  • Re: Please pull ACPI updates
    ... One thing I wish I had in git is a way to make this sequence easier... ... Then I create a new topic branch at the broken patch. ... stable point before the place you want to fix up. ... The normal action is to "pick" the commit. ...
    (Linux-Kernel)
  • Re: Broken "make install" in 2.6.14-git1
    ... > I'm unable to locate that commit, perhaps due to a local lack of gittiness. ... I'm not very good with git. ... All that bisect visualize shows for the patch is the following: ... send the line "unsubscribe linux-kernel" in ...
    (Linux-Kernel)