patch-src_cmd.pl and patch-src_slib.c were removed
what they fix have been fixed upstream.
From bitkeeper release notes:
BitKeeper version 7.3.3 released Dec 29 2018
A bugfix release, but fixes build issues on current systems
- This release fixes some problems where bk fails to build correctly
with newer versions of glibc. (conflict with symbol FILE) And it
needed fixes to work with gperf v3
- 'bk relink' could assert in a certain corner case
`bk: remap.c:119: remap_lstat: Assertion sccs failed.`
- Fix a bug where 'bk cp' didn't work correctly when run from outside
of a the repository containing the file being copied.
- Fix 'bk changes --html' to handle quoting in comments.
Also fix html tag order
- difftool would use the wrong timestamp when extracting data from bk
history. This used to work in the past but was broken with a
different bug was fixed.
- Fixed a bug where 'bk collapse' could corrupt a repository by
removing some required tags.
***
BitKeeper version 7.3.2 released Sep 23 2017
A small collection of bugfixes
- Improve the error message when bk fails to allocate a temp file
https://users.bitkeeper.org/t/read-only-file-system-causes-suboptimal-error-message/478
- Clear BK_CONFIG before running regressions
https://users.bitkeeper.org/t/bk-config-checkout-get-makes-bk-fail-tests/563
- Relax the consistency tests for tags to allow strange constructs
created by 15 year old versions of bk. These will still be rejected
on a newer repository.
- In `bk changes URL`, fix problem with extremely long output lines
not getting transmitted correctly.
https://users.bitkeeper.org/t/bk-changes-path-stops-when-it-hits-a-maximally-long-comment/542
- Document 'bk export -a' that includes files from the `BitKeeper/`
subdirectory and fix a problem where it didn't work with the
`-tpatch` option.
https://users.bitkeeper.org/t/bk-export-omits-changes-to-bitkeeper-etc-ignore/344
- Minor tweaks to fix testcases to continue working correctly
- bkd commands are now able to rotate logfiles to prevent
BitKeeper/log from growing too large
- Testcase tweak to avoid occasional regression failures
https://users.bitkeeper.org/t/occasional-regression-failure-upgrade-running-in-deleted-dir/577/2
- More documentation for 'bk changes --oneline/--short'
***
BitKeeper version 7.3.1ce released Sep 29 2016
A smaller collection of bugfixes and new features. This is mainly
being released because of a bug introducted in bk-7.3 that caused some
older 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 even
if it just does nothing. The reason: if your command is potentially
destructive and it doesn't handle --help, it just ignores it, that
could lead to a mess.
- The dspec expression `$first(:KEY:)` was introduced in bk-7.0 but with a
different less useful syntax. Now `$first()` has changed and is documented.
- The `bk send` and `bk receive` commands will now correctly package
csets from a nested repositories that impact multiple
components. With this release nested csets can be transferred like
this:
```
bk send -rRANGE - | <send to new machine> | bk receive -
```
- The 'changes' command has new --short and --oneline command line
options. See 'bk help changes' for details.
Changes
- In the past, when running 'bk foo' where 'foo' is not a builtin
BitKeeper command, the bk executable would try to execute 'foo' from
the user's PATH. This could cause confusion and so this feature has
been removed. Now and commands that are not understood by BitKeeper,
or match the new bk-foo extention above, will print a command not
found 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 user
running the import after the hostname like this:
`someone@company.com[me]`
This change introduced a bug where old csets created with that
syntax were not read correctly if the repository was also in the OLD
bk-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 now
correctly expanded using historical pathnames when fetch old
versions of files that have been renamed. This was preventing
`bk export -tplain -rREV DIR` for generating a perfect replicate
of older releases that contain keywords.
- In BK/Web when looking at files changes, binary files are not
reported correctly.
80da78e057