From: Larry McVoy <lm@bitmover.com>
To: linux-kernel@vger.kernel.org, bitkeeper-announce@work.bitmover.com
Subject: BK-3.2.3 released
Date: Sat, 14 Aug 2004 22:10:37 -0700 [thread overview]
Message-ID: <20040815051037.GA3795@work.bitmover.com> (raw)
Release notes in the download area. Notable new features are
- commit templates
- tabwidth configuration for you non-8 char folks
- import -tpatch sent in by Stephen Hemminger
- put the BK bin back in the path at the end when calling a trigger
- bk clean will no clean things which were just chmod +w and have no diffs
- some performance fixes for large ChangeSet files (i.e., linux kernel)
Enjoy and let us know what doesn't work.
--
---
Larry McVoy lm at bitmover.com http://www.bitkeeper.com
reply other threads:[~2004-08-15 5:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20040815051037.GA3795@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
all inboxes | Powered by JetHome®