BitKeeper version 7.3.1ce released Sep 29 2016

A smaller collection of bugfixes and new features. This is mainlybeing released because of a bug introducted in bk-7.3 that caused someolder repositories to stop working.

New features

Add a simple mechinism for users to add new commands to BitKeeper.If 'bk-foo' exists on the PATH, then 'bk foo' will call that command.(git already does something similar)If you want 'bk help foo' to work, you do that by making 'bk-foo --help'produce whatever help you want. Your command must handle --help evenif it just does nothing. The reason: if your command is potentiallydestructive and it doesn't handle --help, it just ignores it, thatcould lead to a mess.

The dspec expression $first(:KEY:) was introduced in bk-7.0 but with adifferent less useful syntax. Now $first() has changed and is documented.

The bk send and bk receive commands will now correctly packagecsets from a nested repositories that impact multiplecomponents. With this release nested csets can be transferred likethis:

bk send -rRANGE - | <send to new machine> | bk receive -

The 'changes' command has new --short and --oneline command lineoptions. See 'bk help changes' for details.

Changes

In the past, when running 'bk foo' where 'foo' is not a builtinBitKeeper command, the bk executable would try to execute 'foo' fromthe user's PATH. This could cause confusion and so this feature hasbeen removed. Now and commands that are not understood by BitKeeper,or match the new bk-foo extention above, will print a command notfound error.

The dspec language used to extract metadata with 'bk changes' and'bk log' is now better documented in the 'bk help log' man page.

Bugfixes

In bk-7.3ce, a feature was removed where imports might put the userrunning the import after the hostname like this:someone@company.com[me]This change introduced a bug where old csets created with thatsyntax were not read correctly if the repository was also in the OLDbk-5.0 syntax.

Fix a problem with incremental fast-export on nested repositories

Lots of fixes to the Makefile's to support parallel builds.

Pathnames in RCS and SCCS keywords (see bk help keywords) are nowcorrectly expanded using historical pathnames when fetch oldversions of files that have been renamed. This was preventingbk export -tplain -rREV DIR for generating a perfect replicateof older releases that contain keywords.

In BK/Web when looking at files changes, binary files are notreported correctly.