gitbuster 2.1b2

Safe try

With the demo.sh you can try gitbuster in a safe environment. The script will check that all dependencies are met and install GitPython in a virtualenv. That way it won’t interfere with your system packaging tools (like apt).

Installing From PyPI

Installing with pip:

$ pip install gitbuster

Manual Installation

Get the code:

$ git clone --recursive git://github.com/mike-perdide/gitbuster.git
$ cd gitbuster

Installing

$ make install

Building From Sources

Dependencies:

• pyuic4: on debian/ubuntu systems, look for a package named ‘pyqt4-dev-tools’.

• gcc: on most systems, look for a package named ‘gcc’.

• make: on most systems, look for a package named ‘make’.

• gfbi_core: see https://github.com/mike-perdide/gfbi_core.

• GitPython

To build gitbuster UI files:

$ cd gitbuster/
$ make

To launch gitbuster:

$ export PYTHONPATH=$PYTHONPATH:<path_to_>/gitbuster
$ cd gitbuster
$ ./gitbuster

Bugs

There are bugs in gitbuster, especially in:

• dealing with some unicode commit metadata

• cherry-picking big commits (+10 modified files) may result in gitbuster being blocked

If you find any bug, don’t hesitate to report it and/or send patches:

• on freenode, channel #gitbuster or directly to me (mike_perdide).

• by email: mike dot perdide at gmail dot com

• on github: https://github.com/mike-perdide/gitbuster/issues/new

Please mention the version you’re using, or the tip of the repository if you’re using the development version, and the steps to reproduce. Your help will be greatly appreciated.

Warning

As of v2.1, gitbuster now handles merge commits correctly instead of deleting them as “git rebase -i” would. You can modifiy metadata of an old commit without worrying that it would mess up your history tree. However, you should be careful when reordering commits in a non flat history, as gitbuster doesn’t display correctly the branched histories. The rule of thumb is that inserting a commit in a branch will take the commit below in the tableView as reference: the inserted commit inserted will take its place, and the reference commit will become the inserted commit’s parent. All commits that had the reference commit has parent will now have the inserted commit as parent.