git/list[1] front-page[2] threads[3] people[4] search[5] about
 

ANNOUNCE gitslave-1.1.1 and git-what-branch-0.2.4

From
SRSeth Robertson <in-gitvger@baka.org>
Date
Oct 29, 2010, 20:41 UTC
Message-ID
<201010292041.o9TKfAPL004629@no.baka.org>

gitslave http://gitslave.sf.net is a superproject multi-repository management tool. It creates a group of related repositories--a superproject repository and a number of slave repositories--all of which are concurrently developed on and on which all git operations should normally operate; so when you branch, each repository in the project is branched in turn. Similarly when you commit, push, pull, merge, tag, checkout, status, log, etc; each git command will run on the superproject and all slave repositories in turn.

git-what-branch http://github.com/SethRobertson/git-what-branch determines if a commit was made directly on any named branch/reference, or what the earliest merge path was to a named branch/reference.

Gitslave release notes: ---------------------------------------------------------------------- Add support for `gits remote add` to add new remotes for all slaves with the correct relative remote URLs.

Add support for `gits archive` to generate a unified tarball with slave-relative paths.

Full (and documented) support for command substitution to allow gits-archive, gits-exec, gits-bundle and friends to have output files contain repository specific tokens.

Deduplicate output summarizing code. Provide standard mechanism to suppress (and show) empty command output. ----------------------------------------------------------------------

Git-what-branch release notes: ---------------------------------------------------------------------- Add --first-parent and --first-parent-simple options to allow more easy programmatic detection of failure if a commit was not made directly on any named branch and programmatic parse of output.

Exit with errors if things go wrong or at least not as the user probably desired (e.g. commit has not merged with a named branch, etc)

Bugfix: Prevent duplicate refs from being researched multiple times.
Prevent first-parent outputs from being discussed again during
merge-path output if --all is used.
Bugfix: If multiple commits are listed for research, do not have
subsequent commits inherit bad or duplicate information from previous
commits.
Bugfix: Do not fail if user is not on a branch.
----------------------------------------------------------------------
Message 1 of 1 in “ANNOUNCE gitslave-1.1.1 and git-what-branch-0.2.4”
  1. Seth RobertsonOct 29, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.