Bazaar VCS 1.5rc1 (Default branch)


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News Bazaar VCS 1.5rc1 (Default branch)
# 1  
Old 05-10-2008
Bazaar VCS 1.5rc1 (Default branch)

Bazaar is a simple decentralized revision control system. Decentralized revision control systems give users the ability to branch remote repositories to a local context. Users can commit to local branches without requiring special permission from the branches that they branched from.License: GNU General Public License (GPL)Changes:
This is mostly a bugfix release, with a few moreperformance improvements (for bzr diff and bzrstatus with pending merges). Several performanceimprovements were made, impacting bzr diff, bzrstatus, and bzr pull. The conversion fromdirstate/pack branches into rich-root(pack) hasbeen improved, paving the way for rich-root-packto become the default format within the next fewreleases. This will make interoperating with asubversion repository more seemless, as bzr-svnhas required local repositories to be inrich-root(-pack) formats. User and developerdocumentation have both been expanded.Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread
Login or Register to Ask a Question
ARCHPATH(1)						      General Commands Manual						       ARCHPATH(1)

NAME
archpath - output arch (tla/Bazaar) archive names, with support for branches SYNOPSIS
archpath archpath branch archpath branch--version DESCRIPTION
archpath is intended to be run in an arch (tla or Bazaar) working copy. In its simplest usage, archpath with no parameters outputs the package name (archive/category--branch--version) associated with the working copy. If a parameter is given, it may either be a branch--version, in which case archpath will output a corresponding package name in the current archive and category, or a plain branch name (without '--"), in which case archpath will output a corresponding package name in the current archive and category and with the same version as the current working copy. This is useful for branching. For example, if you're using Bazaar and you want to create a branch for a new feature, you might use a com- mand like this: baz branch $(archpath) $(archpath new-feature) Or if you want to tag your current code onto a 'releases' branch as version 1.0, you might use a command like this: baz branch $(archpath) $(archpath releases--1.0) That's much easier than using 'baz tree-version' to look up the package name and manually modifying the result. AUTHOR
archpath was written by Colin Watson <cjwatson@debian.org>. Like archpath, this manual page is released under the GNU General Public License, version 2 or later. DEBIAN
Debian Utilities ARCHPATH(1)