public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Larry McVoy <lm@bitmover.com>
To: bitkeeper-announce@work.bitmover.com
Cc: linux-kernel@vger.kernel.org
Subject: bk-3.2.0 released
Date: Tue, 18 May 2004 16:32:38 -0700	[thread overview]
Message-ID: <20040518233238.GC28206@work.bitmover.com> (raw)

BitKeeper Users,

BK/Pro 3.2.0 has been released and is in the BK download area,

    http://bitmover.com/download

We're departing from our previous tradition of letting the word out slowly,
people didn't like that.  Because of that, we suggest that cautious users
wait for a week or two to make sure that any lingering bugs have been caught.
The rest of you go bang on it and let us know if we missed anything please.

As always, please use "bk sendbug" to file any bug reports for this
release.

The next effort from us will be a commercial release we hope to have
out in mid-summer.

Thanks and enjoy,

The BitKeeper Team

===============================================================================
Release notes for BitKeeper version 3.2.0.   These release notes cover
the following topics:

. Upgrade Notes
. New Features
. Noteworthy bug fixes

Upgrade notes
----------------------------------------------------------------------------

  On Microsoft Windows, BitKeeper no longer requires (or uses) Cygwin.
  You may use Cygwin if you like but BitKeeper does not need it; BK
  is completely self contained.  

  Registry management, uninstall, and upgrades should work substantially
  better than they have in the past.

New Features
----------------------------------------------------------------------------

  A simple pager called 'bk more' is included and will be used if no
  suitable pager can be found.

  Under Windows the SCCS dirs are now created with the "hidden" attribute.

  HPUX 11.11 is now a supported platform.

  A new command called 'bk lease'.  This is primarily for openlogging users.
  Please see 'bk helptool lease' for more information.

Noteworthy Bug Fixes
----------------------------------------------------------------------------

  2004-01-19-002: Fix resolve bug where 'vr' (view remote) didn't work
  2004-01-27-001: Fix include/exclude processing in 'bk export'
  2004-02-06-002: bk export: fix error case for missing src directory
  2004-03-12-001: Don't delete a RESYNC directory we didn't create
  2004-04-19-001: Fix regression in bk send
  2004-04-23-001: Fix HTTP requests to match standards
  
  Remove an extra unneeded consistency check on the first commit
  after every clone.

  Fixed bug in citool that causes comments for pending files to not
  show up in the bottom window when the ChangeSet file is selected.

  Fix problem in BkWeb where the "N weeks" times didn't match
  reality.

  Improve documentation for which characters are legal in tags and add more
  error checks on tag names.
						   
  Prevent people from passing bad options to 'bk comments'.
  
  Always write keys to BitKeeper/etc/csets-in instead of revs or
  serial numbers.

  Fix a case where 'bk repogca' could return the wrong answer.

  Fix case where BitKeeper didn't work correctly with PGP 8.0 on
  Windows.

  Set time stamps correctly after running 'bk fix'.

-- 
---
Larry McVoy                lm at bitmover.com           http://www.bitkeeper.com

             reply	other threads:[~2004-05-18 23:32 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-18 23:32 Larry McVoy [this message]
2004-05-19  6:51 ` bk-3.2.0 released Christoph Hellwig
2004-05-19 14:02   ` Larry McVoy
2004-05-19 14:11     ` Jan-Benedict Glaw
2004-05-19 14:16       ` Larry McVoy
2004-05-19 14:23         ` Kevin P. Fleming
2004-05-19 14:36           ` John Bradford
2004-05-19 18:47             ` Tomas Szepe
2004-05-19 14:26         ` Jan-Benedict Glaw
2004-05-19 14:48           ` Larry McVoy
2004-05-19 15:00             ` Jan-Benedict Glaw
2004-05-19 15:09               ` Larry McVoy
2004-05-19 16:10                 ` Nicolas Pitre
2004-05-19 20:06           ` Valdis.Kletnieks
2004-05-19 21:20             ` Stan Bubrouski
2004-05-19 14:33         ` Christoph Hellwig
2004-05-19 14:32     ` Christoph Hellwig
2004-05-19 14:34     ` John Bradford
2004-05-19 15:41   ` Bill Davidsen
2004-05-20  3:10   ` Jeff Sipek
2004-05-29  9:54 ` Vojtech Pavlik
2004-05-29 13:04   ` Larry McVoy
2004-05-29 13:15     ` Hugo Mills
2004-05-29 13:20       ` Larry McVoy
2004-05-29 15:47       ` Larry McVoy
2004-05-29 20:13         ` Bryan O'Sullivan
2004-05-30  3:59         ` David Lang
2004-05-29 13:20     ` Vojtech Pavlik

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20040518233238.GC28206@work.bitmover.com \
    --to=lm@bitmover.com \
    --cc=bitkeeper-announce@work.bitmover.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox