direct-io.hg
changeset 2:6c40ab0c10ae
bitkeeper revision 1.1 (3ddb6b0c6FeYAg9nt1aGPFifRbv9-Q)
Initial repository create
Initial repository create
author | smh22@boulderdash.cl.cam.ac.uk |
---|---|
date | Wed Nov 20 10:59:23 2002 +0000 (2002-11-20) |
parents | 5643622fb9a0 |
children | 1ef2026299c3 |
files | .rootkeys BitKeeper/etc/config BitKeeper/etc/ignore |
line diff
1.1 --- a/.rootkeys Wed Nov 20 10:59:23 2002 +0000 1.2 +++ b/.rootkeys Wed Nov 20 10:59:23 2002 +0000 1.3 @@ -0,0 +1,2 @@ 1.4 +3ddb6b0bKlMz_dz-M59a1mkUa1lASw BitKeeper/etc/config 1.5 +3ddb6b0buTaC5zg1_a8FoAR9FWi_mw BitKeeper/etc/ignore
2.1 --- /dev/null Thu Jan 01 00:00:00 1970 +0000 2.2 +++ b/BitKeeper/etc/config Wed Nov 20 10:59:23 2002 +0000 2.3 @@ -0,0 +1,102 @@ 2.4 +# This is the BitKeeper configuration for this package. 2.5 +# 2.6 +# Please take a minute to fill it out carefully, it needs to be accurate. 2.7 +# 2.8 +# NOTICE: you really do want to fill this out, if something goes wrong 2.9 +# with your repository, or if someone changes the logging policy, we 2.10 +# send mail to the contact listed here for confirmation. 2.11 +# 2.12 +# BitKeeper can maintain a log of your change comments (not your source, 2.13 +# just the comments) on a centralized server. This is useful as your 2.14 +# project grows, it gives people a place to go see what is happening on 2.15 +# a per project basis. This is especially useful for distributed developers. 2.16 +# 2.17 + 2.18 +# 2.19 +# Name of the project, such as "BitKeeper" or "The GNU C compiler". 2.20 +# 2.21 +description: XenoServer Source 2.22 +# 2.23 +# What (RedHat package) category this project fits into, if any. 2.24 +# 2.25 +category: 2.26 +# 2.27 +# Open Logging server. This site is where users go to see the 2.28 +# ChangeSet comments for all instances of this repository. This must 2.29 +# be logging@openlogging.org for usage under the terms of the BKL, 2.30 +# "bk help bkl" will show you the default licensing terms. If this 2.31 +# repository is commercial it can be an internal email address or "none" 2.32 +# to disable logging. 2.33 +# 2.34 +logging: logging@openlogging.org 2.35 +# 2.36 +# You do not have a license for BitKeeper and the logging field in the 2.37 +# BitKeeper/etc/config file is not set to "logging@openlogging.org". 2.38 +# You either need a commercial license (to run without open logging), 2.39 +# or you need to convert your package to single user, or you need to 2.40 +# configure your package to use openlogging. Until you have done one of 2.41 +# those, you may not create any changesets. 2.42 +# 2.43 +# You can get a temporary license by sending a mail request 2.44 +# to sales@bitmover.com. 2.45 +# 2.46 +# BitMover can be reached in the United States at 415-401-8808 2.47 +# during business hours (PST) or via email at sales@bitmover.com. 2.48 +# Thanks! 2.49 +license: 2.50 +licsign1: 2.51 +licsign2: 2.52 +licsign3: 2.53 +# 2.54 +# If this field is set, all checkins will appear to be made by this user, 2.55 +# in effect making this a single user package. Single user packages are 2.56 +# free from the logging constraint up to a maximum of 1000 files. In order 2.57 +# for the package to really be free, both the single_user and the single_host 2.58 +# field need to be set. 2.59 +# 2.60 +single_user: 2.61 +# 2.62 +# If this field is set, all checkins will appear to be made on this host. 2.63 +# 2.64 +single_host: 2.65 +# 2.66 +# Default compression algorithm for stored s.files is gzip. 2.67 +# If you want no compression, set this to "none". 2.68 +# 2.69 +compression: gzip 2.70 +# 2.71 +# Default is to autofix problems found by check. 2.72 +# If you want to manually fix them, set this to "no". 2.73 +# 2.74 +autofix: yes 2.75 +# 2.76 +# Contact person for this project. This is whoever is the person that 2.77 +# should be contacted with update information or contacted if BitKeeper 2.78 +# discovers a problem which requires local intervention. Please make the 2.79 +# contact information accurate so we can support you. 2.80 +# 2.81 +contact: Steven Hand 2.82 +# 2.83 +# It is very important that this email address is filled out and accurate. 2.84 +# If someone converts your repository to open logging (which you may not 2.85 +# want), we will contact this email address for confirmation that you really 2.86 +# did want open logging. If the email address is inaccurate and we get no 2.87 +# response from anyone else at your location after 90 days, then open logging 2.88 +# will be implicitly approved. 2.89 +# 2.90 +email: bk+steven.hand@cl.cam.ac.uk 2.91 +# 2.92 +# Add your street address if you like, it is optional. 2.93 +# 2.94 +street: 2.95 +city: 2.96 +state: 2.97 +postal: 2.98 +country: 2.99 +phone: 2.100 +cell: 2.101 +pager: 2.102 +# 2.103 +# Business Hours when we can contact you if you left a phone number. 2.104 +# 2.105 +hours: