{"thread":{"id":"18155","subject":"[ANNOUNCE] TopGit 0.7","startedAt":"2009-03-05T20:27:09Z","lastAt":"2009-03-06T02:04:02Z","messageCount":4,"participants":["Uwe Kleine-König","Mark Wilden"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"107095","messageId":"20090305202709.GB15486@pengutronix.de","threadId":"18155","inReplyTo":null,"subject":"[ANNOUNCE] TopGit 0.7","fromName":"Uwe Kleine-König","fromEmail":"u.kleine-koenig@pengutronix.de","sentAt":"2009-03-05T20:27:09Z","receivedAt":"2009-03-05T20:27:09Z","isPatch":false,"sender":{"key":"u.kleine-koenig@pengutronix.de","avatar":"https://gravatar.com/avatar/354b5e3ceb2806a2f1e1e382ac29ddbdad18288654da62b61eb13583a857eee7?d=mp&s=160"},"body":"Hello *,\n\nI'm happy to announce that TopGit 0.7 was released today.\n\nThis release brings you several bug fixes and a few new features.\n\nThe most useful new feature (in my opinon) is a new export method that\nprovides your patches as a linear history in a regular git branch for\npulling by your upstream.\n\nTopGit aims to make handling of large amount of interdependent topic\nbranches easier. In fact, it is designed especially for the case when\nyou maintain a queue of third-party patches on top of another (perhaps\nGit-controlled) project and want to easily organize, maintain and submit\nthem - TopGit achieves that by keeping a separate topic branch for each\npatch and providing few tools to maintain the branches\n\nYou can get TopGit at\n\n\thttp://repo.or.cz/w/topgit.git\n\nor if you run Debian you can install the version from the\nunstable distribution[*1*].\n\nIf you want to read more about TopGit's design, usage and\nimplementation, let me point you to TopGit's README at\n\n\thttp://repo.or.cz/w/topgit.git?a=blob;f=README\n\nThe full shortlog since version TopGit 0.5[*2*] can be found below.\n\nI would be happy if you gave it a try and reported your impressions,\nsuggestions and bugs.\n\nBest regards\nUwe\n\n[*1*] Up to now it didn't hit unstable, but if you cannot wait for a few\n      hours you have to install from source :-)\n\n[*2*] Version 0.6 was skipped, because a change bumping the version\n      number was accidently pushed to a public repo.  As the latest\n      version get some more changes, we decided to skip to 0.7.\n\nBert Wesarg (1):\n      tg-summary: -t and --graphviz are mutual exclusive\n\nJonas Fonseca (1):\n      README: spelling fixes\n\nKirill Smelkov (5):\n      tg-completion: complete options for `tg summary`\n      tg-completion: complete options for `tg remote`\n      Implement setup_pager just like in git\n      tg-patch: fix pagination\n      tg-patch: add support for generating patches against worktree and index\n\nMarc Weber (1):\n      Pass -- to rev-list for branch/filename disambiguation\n\nUwe Kleine-König (15):\n      tg-export: implement skipping empty patches for quilt mode\n      tg export (collapse): implement skipping empty patches\n      tg export (quilt): Implement flattening patch paths\n      tg export (quilt): Implement numbering the patches\n      make tg remote idempotent\n      [TOPGIT] limit rev-list in branch_contains to a single rev\n      [TOPGIT] allow working with annihilated branches\n      [TOPGIT] make tg remote idempotent\n      [TOPGIT] make creating a commit from a topgit branch a function\n      [TOPGIT] implement linearize export method\n      Don't throw away already started base on resumed create.\n      Add documentation for tg export --linearize\n      Merge branch 'upstream' of git.debian.org:/git/collab-maint/topgit\n      Fix typo s/emmail/email/\n      bump version number to 0.7\n\nmartin f. krafft (14):\n      ignore tg-depend build files\n      remove +x bit from tg-depend\n      Make sure gitignore patterns are not recursive\n      add ignore patterns for quilt and debian build\n      Change tg help exit code to 0\n      Check for cmddir earlier\n      Print help output when no command is given\n      Require an argument to tg -r\n      Print help message when command is not proper\n      Note that do_help is used when short messages might be wanted\n      Add Vim modelines for consistent spacing\n      Check for git-send-email and die if not found\n      put tg version into a variable at the top\n      bump version number to 0.6\n\n-- \nPengutronix e.K.                              | Uwe Kleine-König            |\nIndustrial Linux Solutions                    | http://www.pengutronix.de/  |\n"},{"id":"107096","messageId":"20090305203103.GC15486@pengutronix.de","threadId":"18155","inReplyTo":"20090305202709.GB15486@pengutronix.de","subject":"Re: [ANNOUNCE] TopGit 0.7","fromName":"Uwe Kleine-König","fromEmail":"u.kleine-koenig@pengutronix.de","sentAt":"2009-03-05T20:31:03Z","receivedAt":"2009-03-05T20:31:03Z","isPatch":false,"sender":{"key":"u.kleine-koenig@pengutronix.de","avatar":"https://gravatar.com/avatar/354b5e3ceb2806a2f1e1e382ac29ddbdad18288654da62b61eb13583a857eee7?d=mp&s=160"},"body":"Hello again,\n\nsomething I forgot to mention in the previous mail:  We installed a\nchannel #topgit on freenode's irc network.\n\nIf you're interested in TopGit, have questions, problems or suggestions,\njoin us there.\n\nBest regards\nUwe\n\n-- \nPengutronix e.K.                              | Uwe Kleine-König            |\nIndustrial Linux Solutions                    | http://www.pengutronix.de/  |\n"},{"id":"107097","messageId":"3c30da400903051245j2f89a136m95cdae3c64292024@mail.gmail.com","threadId":"18155","inReplyTo":"20090305202709.GB15486@pengutronix.de","subject":"Re: [ANNOUNCE] TopGit 0.7","fromName":"Mark Wilden","fromEmail":"mark@mwilden.com","sentAt":"2009-03-05T20:45:20Z","receivedAt":"2009-03-05T20:45:20Z","isPatch":false,"sender":{"key":"mark@mwilden.com","avatar":null},"body":"On Thu, Mar 5, 2009 at 12:27 PM, Uwe Kleine-König\n<u.kleine-koenig@pengutronix.de> wrote:\n>\n> I'm happy to announce that TopGit 0.7 was released today.\n>\n> This release brings you several bug fixes and a few new features.\n\nWhen announcing a release, you might consider including a few words\nabout what the project does. There will be people (like me) who were\nnot familiar with it before seeing the release announcement, and this\nwould help them to quickly find out whether it should be investigated.\n\nJust a suggestion - ignore at will. :)\n\n///ark\n"},{"id":"107130","messageId":"3c30da400903051804g50a06512sbe844d473de75913@mail.gmail.com","threadId":"18155","inReplyTo":"3c30da400903051245j2f89a136m95cdae3c64292024@mail.gmail.com","subject":"Re: [ANNOUNCE] TopGit 0.7","fromName":"Mark Wilden","fromEmail":"mark@mwilden.com","sentAt":"2009-03-06T02:04:02Z","receivedAt":"2009-03-06T02:04:02Z","isPatch":false,"sender":{"key":"mark@mwilden.com","avatar":null},"body":"> also sprach Mark Wilden <mark@mwilden.com> [2009.03.05.2145 +0100]:\n>> When announcing a release, you might consider including a few\n>> words about what the project does. There will be people (like me)\n>> who were not familiar with it before seeing the release\n>> announcement, and this would help them to quickly find out whether\n>> it should be investigated.\n\nOops - I didn't see the description of the project. I stopped reading\nbefore I got there. :)\n\n///ark\n"}]}