{"thread":{"id":"25596","subject":"ANNOUNCE gitslave-1.1.1 and git-what-branch-0.2.4","startedAt":"2010-10-29T20:41:10Z","lastAt":"2010-10-29T20:41:10Z","messageCount":1,"participants":["Seth Robertson"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"154813","messageId":"201010292041.o9TKfAPL004629@no.baka.org","threadId":"25596","inReplyTo":null,"subject":"ANNOUNCE gitslave-1.1.1 and git-what-branch-0.2.4","fromName":"Seth Robertson","fromEmail":"in-gitvger@baka.org","sentAt":"2010-10-29T20:41:10Z","receivedAt":"2010-10-29T20:41:10Z","isPatch":false,"sender":{"key":"in-gitvger@baka.org","avatar":null},"body":"\ngitslave http://gitslave.sf.net is a superproject multi-repository\nmanagement tool. It creates a group of related repositories--a\nsuperproject repository and a number of slave repositories--all of\nwhich are concurrently developed on and on which all git operations\nshould normally operate; so when you branch, each repository in the\nproject is branched in turn. Similarly when you commit, push, pull,\nmerge, tag, checkout, status, log, etc; each git command will run on\nthe superproject and all slave repositories in turn.\n\ngit-what-branch http://github.com/SethRobertson/git-what-branch\ndetermines if a commit was made directly on any named\nbranch/reference, or what the earliest merge path was to a named\nbranch/reference.\n\n\nGitslave release notes:\n----------------------------------------------------------------------\nAdd support for `gits remote add` to add new remotes for all slaves\nwith the correct relative remote URLs.\n\nAdd support for `gits archive` to generate a unified tarball with\nslave-relative paths.\n\nFull (and documented) support for command substitution to allow\ngits-archive, gits-exec, gits-bundle and friends to have output files\ncontain repository specific tokens.\n\nDeduplicate output summarizing code.  Provide standard mechanism to\nsuppress (and show) empty command output.\n----------------------------------------------------------------------\n\n\nGit-what-branch release notes:\n----------------------------------------------------------------------\nAdd --first-parent and --first-parent-simple options to allow more\neasy programmatic detection of failure if a commit was not made\ndirectly on any named branch and programmatic parse of output.\n\nExit with errors if things go wrong or at least not as the user\nprobably desired (e.g. commit has not merged with a named branch, etc)\n\nBugfix: Prevent duplicate refs from being researched multiple times.\nPrevent first-parent outputs from being discussed again during\nmerge-path output if --all is used.\n\nBugfix: If multiple commits are listed for research, do not have\nsubsequent commits inherit bad or duplicate information from previous\ncommits.\n\nBugfix: Do not fail if user is not on a branch.\n----------------------------------------------------------------------\n"}]}