[ANNOUNCE] TopGit 0.7

Hello *,

I'm happy to announce that TopGit 0.7 was released today.

This release brings you several bug fixes and a few new features.

The most useful new feature (in my opinon) is a new export method that provides your patches as a linear history in a regular git branch for pulling by your upstream.

TopGit aims to make handling of large amount of interdependent topic branches easier. In fact, it is designed especially for the case when you maintain a queue of third-party patches on top of another (perhaps Git-controlled) project and want to easily organize, maintain and submit them - TopGit achieves that by keeping a separate topic branch for each patch and providing few tools to maintain the branches

You can get TopGit at

	http://repo.or.cz/w/topgit.git

or if you run Debian you can install the version from the unstable distribution[*1*].

If you want to read more about TopGit's design, usage and implementation, let me point you to TopGit's README at

	http://repo.or.cz/w/topgit.git?a=blob;f=README

The full shortlog since version TopGit 0.5[*2*] can be found below.

I would be happy if you gave it a try and reported your impressions, suggestions and bugs.

Best regards Uwe

[*1*] Up to now it didn't hit unstable, but if you cannot wait for a few
      hours you have to install from source :-)

[*2*] Version 0.6 was skipped, because a change bumping the version
      number was accidently pushed to a public repo.  As the latest
      version get some more changes, we decided to skip to 0.7.

Bert Wesarg (1):
      tg-summary: -t and --graphviz are mutual exclusive

Jonas Fonseca (1):
      README: spelling fixes

Kirill Smelkov (5):
      tg-completion: complete options for `tg summary`
      tg-completion: complete options for `tg remote`
      Implement setup_pager just like in git
      tg-patch: fix pagination
      tg-patch: add support for generating patches against worktree and index

Marc Weber (1):
      Pass -- to rev-list for branch/filename disambiguation

Uwe Kleine-König (15):
      tg-export: implement skipping empty patches for quilt mode
      tg export (collapse): implement skipping empty patches
      tg export (quilt): Implement flattening patch paths
      tg export (quilt): Implement numbering the patches
      make tg remote idempotent
      [TOPGIT] limit rev-list in branch_contains to a single rev
      [TOPGIT] allow working with annihilated branches
      [TOPGIT] make tg remote idempotent
      [TOPGIT] make creating a commit from a topgit branch a function
      [TOPGIT] implement linearize export method
      Don't throw away already started base on resumed create.
      Add documentation for tg export --linearize
      Merge branch 'upstream' of git.debian.org:/git/collab-maint/topgit
      Fix typo s/emmail/email/
      bump version number to 0.7

martin f. krafft (14):
      ignore tg-depend build files
      remove +x bit from tg-depend
      Make sure gitignore patterns are not recursive
      add ignore patterns for quilt and debian build
      Change tg help exit code to 0
      Check for cmddir earlier
      Print help output when no command is given
      Require an argument to tg -r
      Print help message when command is not proper
      Note that do_help is used when short messages might be wanted
      Add Vim modelines for consistent spacing
      Check for git-send-email and die if not found
      put tg version into a variable at the top
      bump version number to 0.6

Hello again,

something I forgot to mention in the previous mail: We installed a channel #topgit on freenode's irc network.

If you're interested in TopGit, have questions, problems or suggestions, join us there.

Best regards Uwe

On Thu, Mar 5, 2009 at 12:27 PM, Uwe Kleine-König <u.kleine-koenig@pengutronix.de> wrote:

When announcing a release, you might consider including a few words about what the project does. There will be people (like me) who were not familiar with it before seeing the release announcement, and this would help them to quickly find out whether it should be investigated.

Just a suggestion - ignore at will. :)

///ark

Oops - I didn't see the description of the project. I stopped reading before I got there. :)

///ark