Version Control Blog

Stacked GIT 0.11 release is available from http://www.procode.org/stgit/. StGIT is a Python application providing similar functionality to Quilt (i.e. pushing/popping patches to/from a stack) on top of GIT. These operations are performed using GIT commands and the patches are stored as GIT commit objects, allowing easy merging of the StGIT patches into other repositories using standard GIT functionality.

The latest feature release GIT 1.4.3 is available at the usual places: http://www.kernel.org/pub/software/scm/git/ User visible changes, other than bugfixes, since v1.4.2.4 are: - upload-tar is deprecated but not removed; we now have upload-archive –format=tar and –format=zip instead. - ftp:// protocol is supported the same way as http:// and https:// - git-diff paginates its output to the tty by default. If this irritates you, using LESS=RF might help. - git-cherry-pick does not leave often useless “cherry-picked from” message. - git-merge-recursive was replaced by a rewritten implemention in C. The original Python implementation is available as “recursive-old” strategy for now, but hopefully we can remove it in the next cycle. - git-daemon can do name based virtual hosting. - git-daemon can serve tar and zip snapshots. - many gitweb tweaks and cleanups. - git-apply –reverse, –reject. - git-diff –color highlights whitespace errors. - git-diff –stat can be taught to use non-default widths. - git-status can use colors. - many more commands are built-in.

The latest maintenance release GIT 1.4.3.1 is available at the usual places: http://www.kernel.org/pub/software/scm/git/ This is primarily to work around changes in the recent GNU diff output format. Also it contains irritation fix for “git diff” which now paginates its output by default.

The monotone team is pleased to announce the release of monotone 0.30, available, as always, from http://venge.net/monotone with more binary packages appearing there as they are built. The release notes for this release are: Sun Sep 17 12:27:08 PDT 2006 0.30 release. Speed improvements, bug fixes, and improved infrastructure. Several internal data formats have changed with this release; migration is straight-forward, but slightly more complicated than usual: — The formats used to store some cached data in the database have changed. To upgrade your databases, you must run: $ mtn -d mydb.mtn db migrate $ mtn -d mydb.mtn db regenerate_rosters — The metadata stored in _MTN in each workspace has been rearranged slightly. To upgrade your workspaces, you must run $ mtn migrate_workspace in each workspace. All of these operations are completely lossless, and 0.30 remains compatible with earlier versions with regards to netsync.