head	1.11;
access;
symbols
	RELENG_8_4:1.11.0.2
	RELENG_9_1_0_RELEASE:1.10.42.1.4.2
	RELENG_9_1:1.10.42.1.0.4
	RELENG_9_1_BP:1.10.42.1
	RELENG_8_3_0_RELEASE:1.10.36.1.8.1
	RELENG_8_3:1.10.36.1.0.8
	RELENG_8_3_BP:1.10.36.1
	RELENG_9_0_0_RELEASE:1.10.42.1.2.1
	RELENG_9_0:1.10.42.1.0.2
	RELENG_9_0_BP:1.10.42.1
	RELENG_9:1.10.0.42
	RELENG_9_BP:1.10
	RELENG_7_4_0_RELEASE:1.10.40.1
	RELENG_8_2_0_RELEASE:1.10.36.1.6.1
	RELENG_7_4:1.10.0.40
	RELENG_7_4_BP:1.10
	RELENG_8_2:1.10.36.1.0.6
	RELENG_8_2_BP:1.10.36.1
	RELENG_8_1_0_RELEASE:1.10.36.1.4.1
	RELENG_8_1:1.10.36.1.0.4
	RELENG_8_1_BP:1.10.36.1
	RELENG_7_3_0_RELEASE:1.10.38.1
	RELENG_7_3:1.10.0.38
	RELENG_7_3_BP:1.10
	RELENG_8_0_0_RELEASE:1.10.36.1.2.1
	RELENG_8_0:1.10.36.1.0.2
	RELENG_8_0_BP:1.10.36.1
	RELENG_8:1.10.0.36
	RELENG_8_BP:1.10
	RELENG_7_2_0_RELEASE:1.10.34.1
	RELENG_7_2:1.10.0.34
	RELENG_7_2_BP:1.10
	RELENG_7_1_0_RELEASE:1.10.32.1
	RELENG_6_4_0_RELEASE:1.10.30.1
	RELENG_7_1:1.10.0.32
	RELENG_7_1_BP:1.10
	RELENG_6_4:1.10.0.30
	RELENG_6_4_BP:1.10
	RELENG_7_0_0_RELEASE:1.10
	RELENG_6_3_0_RELEASE:1.10
	RELENG_7_0:1.10.0.28
	RELENG_7_0_BP:1.10
	RELENG_6_3:1.10.0.26
	RELENG_6_3_BP:1.10
	RELENG_7:1.10.0.24
	RELENG_7_BP:1.10
	RELENG_6_2_0_RELEASE:1.10
	RELENG_6_2:1.10.0.22
	RELENG_6_2_BP:1.10
	RELENG_5_5_0_RELEASE:1.10
	RELENG_5_5:1.10.0.20
	RELENG_5_5_BP:1.10
	RELENG_6_1_0_RELEASE:1.10
	RELENG_6_1:1.10.0.18
	RELENG_6_1_BP:1.10
	RELENG_6_0_0_RELEASE:1.10
	RELENG_6_0:1.10.0.16
	RELENG_6_0_BP:1.10
	RELENG_6:1.10.0.14
	RELENG_6_BP:1.10
	RELENG_5_4_0_RELEASE:1.10
	RELENG_5_4:1.10.0.12
	RELENG_5_4_BP:1.10
	RELENG_4_11_0_RELEASE:1.9
	RELENG_4_11:1.9.0.20
	RELENG_4_11_BP:1.9
	RELENG_5_3_0_RELEASE:1.10
	RELENG_5_3:1.10.0.10
	RELENG_5_3_BP:1.10
	RELENG_5:1.10.0.8
	RELENG_5_BP:1.10
	RELENG_4_10_0_RELEASE:1.9
	RELENG_4_10:1.9.0.18
	RELENG_4_10_BP:1.9
	RELENG_5_2_1_RELEASE:1.10
	RELENG_5_2_0_RELEASE:1.10
	RELENG_5_2:1.10.0.6
	RELENG_5_2_BP:1.10
	RELENG_4_9_0_RELEASE:1.9
	RELENG_4_9:1.9.0.16
	RELENG_4_9_BP:1.9
	RELENG_5_1_0_RELEASE:1.10
	RELENG_5_1:1.10.0.4
	RELENG_5_1_BP:1.10
	RELENG_4_8_0_RELEASE:1.9
	RELENG_4_8:1.9.0.14
	RELENG_4_8_BP:1.9
	RELENG_5_0_0_RELEASE:1.10
	RELENG_5_0:1.10.0.2
	RELENG_5_0_BP:1.10
	RELENG_4_7_0_RELEASE:1.9
	RELENG_4_7:1.9.0.12
	RELENG_4_7_BP:1.9
	RELENG_4_6_2_RELEASE:1.9
	RELENG_4_6_1_RELEASE:1.9
	RELENG_4_6_0_RELEASE:1.9
	RELENG_4_6:1.9.0.10
	RELENG_4_6_BP:1.9
	RELENG_4_5_0_RELEASE:1.9
	RELENG_4_5:1.9.0.8
	RELENG_4_5_BP:1.9
	RELENG_4_4_0_RELEASE:1.9
	RELENG_4_4:1.9.0.6
	RELENG_4_4_BP:1.9
	RELENG_4_3_0_RELEASE:1.9
	RELENG_4_3:1.9.0.4
	RELENG_4_3_BP:1.9
	RELENG_4_2_0_RELEASE:1.9
	RELENG_4_1_1_RELEASE:1.9
	PRE_SMPNG:1.9
	RELENG_4_1_0_RELEASE:1.9
	RELENG_3_5_0_RELEASE:1.7.2.1
	RELENG_4_0_0_RELEASE:1.9
	RELENG_4:1.9.0.2
	RELENG_4_BP:1.9
	RELENG_3_4_0_RELEASE:1.7.2.1
	RELENG_3_3_0_RELEASE:1.7.2.1
	RELENG_3_2_PAO:1.7.0.4
	RELENG_3_2_PAO_BP:1.7
	RELENG_3_2_0_RELEASE:1.7
	RELENG_3_1_0_RELEASE:1.7
	RELENG_3:1.7.0.2
	RELENG_3_BP:1.7
	RELENG_2_2_8_RELEASE:1.4.8.1
	RELENG_3_0_0_RELEASE:1.7
	RELENG_2_2_7_RELEASE:1.4.8.1
	RELENG_2_2_6_RELEASE:1.4
	RELENG_2_2_5_RELEASE:1.4
	RELENG_2_2_2_RELEASE:1.4
	RELENG_2_2_1_RELEASE:1.4
	RELENG_2_2_0_RELEASE:1.4
	RELENG_2_1_7_RELEASE:1.4
	RELENG_2_1_6_1_RELEASE:1.4
	RELENG_2_1_6_RELEASE:1.4
	RELENG_2_2:1.4.0.8
	RELENG_2_2_BP:1.4
	RELENG_2_1_5_RELEASE:1.4
	RELENG_2_1_0_RELEASE:1.4
	RELENG_2_1_0:1.4.0.6
	RELENG_2_1_0_BP:1.4
	RELENG_2_0_5_RELEASE:1.4
	RELENG_2_0_5:1.4.0.4
	RELENG_2_0_5_BP:1.4
	RELENG_2_0_5_ALPHA:1.4
	RELEASE_2_0:1.4
	BETA_2_0:1.4
	ALPHA_2_0:1.4.0.2
	orig:1.1.1.1
	phk:1.1.1;
locks; strict;
comment	@# @;


1.11
date	2012.11.17.01.54.43;	author svnexp;	state Exp;
branches
	1.11.2.1;
next	1.10;

1.10
date	2002.03.25.14.12.09;	author phk;	state Exp;
branches
	1.10.14.1
	1.10.24.1
	1.10.30.1
	1.10.32.1
	1.10.34.1
	1.10.36.1
	1.10.38.1
	1.10.40.1
	1.10.42.1;
next	1.9;

1.9
date	99.11.29.17.58.58;	author markm;	state Exp;
branches
	1.9.2.1;
next	1.8;

1.8
date	99.08.28.01.15.58;	author peter;	state Exp;
branches;
next	1.7;

1.7
date	98.04.20.20.55.43;	author rnordier;	state Exp;
branches
	1.7.2.1;
next	1.6;

1.6
date	97.02.22.16.05.15;	author peter;	state Exp;
branches;
next	1.5;

1.5
date	97.01.14.07.11.24;	author jkh;	state Exp;
branches;
next	1.4;

1.4
date	94.09.22.02.49.07;	author phk;	state Exp;
branches
	1.4.6.1
	1.4.8.1;
next	1.3;

1.3
date	94.09.21.04.38.20;	author phk;	state Exp;
branches;
next	1.2;

1.2
date	94.09.20.07.13.20;	author phk;	state Exp;
branches;
next	1.1;

1.1
date	94.09.19.07.32.21;	author phk;	state Exp;
branches
	1.1.1.1;
next	;

1.11.2.1
date	2012.11.17.01.54.43;	author svnexp;	state dead;
branches;
next	1.11.2.2;

1.11.2.2
date	2013.03.28.13.06.15;	author svnexp;	state Exp;
branches;
next	;

1.10.14.1
date	2012.11.17.07.46.15;	author svnexp;	state Exp;
branches;
next	;

1.10.24.1
date	2012.11.17.08.09.01;	author svnexp;	state Exp;
branches;
next	;

1.10.30.1
date	2008.10.02.02.57.24;	author kensmith;	state Exp;
branches;
next	;

1.10.32.1
date	2008.11.25.02.59.29;	author kensmith;	state Exp;
branches;
next	;

1.10.34.1
date	2009.04.15.03.14.26;	author kensmith;	state Exp;
branches;
next	;

1.10.36.1
date	2009.08.03.08.13.06;	author kensmith;	state Exp;
branches
	1.10.36.1.2.1
	1.10.36.1.4.1
	1.10.36.1.6.1
	1.10.36.1.8.1;
next	1.10.36.2;

1.10.36.2
date	2012.11.17.10.37.22;	author svnexp;	state Exp;
branches;
next	;

1.10.36.1.2.1
date	2009.10.25.01.10.29;	author kensmith;	state Exp;
branches;
next	;

1.10.36.1.4.1
date	2010.06.14.02.09.06;	author kensmith;	state Exp;
branches;
next	;

1.10.36.1.6.1
date	2010.12.21.17.09.25;	author kensmith;	state Exp;
branches;
next	;

1.10.36.1.8.1
date	2012.03.03.06.15.13;	author kensmith;	state Exp;
branches;
next	1.10.36.1.8.2;

1.10.36.1.8.2
date	2012.11.17.08.25.54;	author svnexp;	state Exp;
branches;
next	;

1.10.38.1
date	2010.02.10.00.26.20;	author kensmith;	state Exp;
branches;
next	;

1.10.40.1
date	2010.12.21.17.10.29;	author kensmith;	state Exp;
branches;
next	1.10.40.2;

1.10.40.2
date	2012.11.17.08.17.47;	author svnexp;	state Exp;
branches;
next	;

1.10.42.1
date	2011.09.23.00.51.37;	author kensmith;	state Exp;
branches
	1.10.42.1.2.1
	1.10.42.1.4.1;
next	1.10.42.2;

1.10.42.2
date	2012.11.17.11.37.43;	author svnexp;	state Exp;
branches;
next	;

1.10.42.1.2.1
date	2011.11.11.04.20.22;	author kensmith;	state Exp;
branches;
next	1.10.42.1.2.2;

1.10.42.1.2.2
date	2012.11.17.08.37.40;	author svnexp;	state Exp;
branches;
next	;

1.10.42.1.4.1
date	2012.08.05.23.54.33;	author kensmith;	state Exp;
branches;
next	1.10.42.1.4.2;

1.10.42.1.4.2
date	2012.11.17.08.48.31;	author svnexp;	state Exp;
branches;
next	;

1.9.2.1
date	2012.11.17.07.28.08;	author svnexp;	state Exp;
branches;
next	;

1.7.2.1
date	99.08.29.15.40.54;	author peter;	state Exp;
branches;
next	;

1.4.6.1
date	99.09.05.11.44.08;	author peter;	state Exp;
branches;
next	;

1.4.8.1
date	98.07.18.11.09.35;	author jkh;	state Exp;
branches;
next	1.4.8.2;

1.4.8.2
date	99.09.05.11.40.11;	author peter;	state Exp;
branches;
next	;

1.1.1.1
date	94.09.19.07.32.22;	author phk;	state Exp;
branches;
next	;


desc
@@


1.11
log
@Switching exporter and resync
@
text
@# ----------------------------------------------------------------------------
# "THE BEER-WARE LICENSE" (Revision 42):
# <phk@@FreeBSD.org> wrote this file.  As long as you retain this notice you
# can do whatever you want with this stuff. If we meet some day, and you think
# this stuff is worth it, you can buy me a beer in return.   Poul-Henning Kamp
# ----------------------------------------------------------------------------
#
# $FreeBSD: head/usr.sbin/ctm/README 93151 2002-03-25 14:12:49Z phk $
#

What will I not find in this file ?
-----------------------------------
Instructions on how to obtain FreeBSD via CTM.
Contact <CTM@@FreeBSD.org> for that.

What is CTM ?
-------------
CTM was originally "CVS Through eMail", but has since changed scope to be
much more general.
CTM is now meant to be the definitive way to make and apply a delta between
two versions of a directory tree.
There are two parts to this, making the delta and applying it.  These are two
entirely different things.  CTM concentrates the computation-burden on the
generation of the deltas, as a delta very often is applied more times than
it is made.  Second CTM tries to make the minimal size delta.

Why not use diff/patch ?
------------------------
Good question.  Primarily because diff and patch doesn't do their job very 
well.  They don't deal with binary files (in this case files with '\0' or 
'\0377' characters in them or files that doesn't end in '\n') which isn't
a big surprise:  they were made to deal with text-files only.  As a second
gripe, with patch you send the entire file to delete it.  Not particular
efficient.

So what does CTM do exactly ?
-----------------------------
CTM will produce a file, (a delta) containing the instructions and data needed
to take another copy of the tree from the old to the new status.  CTM means to
do this in the exact sense, and therefore the delta contains MD5 checksums to
verify that the tree it is applied to is indeed in the state CTM expects.

This means that if you have modified the tree locally, CTM might not be able
to upgrade your copy.

How do I make a CTM-delta ?
---------------------------

Read the source, and be prepared to have 2 copies of the tree; One is
the reference ("From") tree, and the other is the delta ("To") tree.
The mkCTM script will create the CTM diff of the differences between
the reference tree and the delta tree. A lot of scratch space is
required, and your machine will work hard.

How do I apply a CTM-delta ?
----------------------------
You pass it to the 'ctm' command.  You can pass a CTM-delta on stdin, or
you can give the filename as an argument.  If you do the latter, you make
life a lot easier for your self, since the program can accept gzip'ed files
and since it will not have to make a temporary copy of your file.  You can
specify multiple deltas at one time, they will be processed one at a time.

The ctm command runs in a number of passes.  It will process the entire
input file in each pass, before commencing with the next pass.

Pass 1 will validate that the input file is OK.  The syntax, the data and 
the global MD5 checksum will be checked.  If any of these fail, ctm will
never be able to do anything with the file, so it will simply reject it.

Pass 2 will validate that the directory tree is in the state expected by
the CTM-delta.  This is done by looking for files and directories which
should/should not exists and by checking the MD5 checksums of files.  

Pass 3 will actually apply the delta.

Should I delete the delta when I have applied it ?
--------------------------------------------------
No.  You might want to selectively reconstruct a file latter on.

Why is CTM not being maintained?
--------------------------------
Because CVSUP has improved on the concept quite a bit, and is now
the method of choice.

Poul-Henning
@


1.11.2.1
log
@file README was added on branch RELENG_8_4 on 2013-03-28 13:06:15 +0000
@
text
@d1 85
@


1.11.2.2
log
@## SVN ## Exported commit - http://svnweb.freebsd.org/changeset/base/248810
## SVN ## CVS IS DEPRECATED: http://wiki.freebsd.org/CvsIsDeprecated
@
text
@a0 85
# ----------------------------------------------------------------------------
# "THE BEER-WARE LICENSE" (Revision 42):
# <phk@@FreeBSD.org> wrote this file.  As long as you retain this notice you
# can do whatever you want with this stuff. If we meet some day, and you think
# this stuff is worth it, you can buy me a beer in return.   Poul-Henning Kamp
# ----------------------------------------------------------------------------
#
# $FreeBSD: releng/8.4/usr.sbin/ctm/README 93151 2002-03-25 14:12:49Z phk $
#

What will I not find in this file ?
-----------------------------------
Instructions on how to obtain FreeBSD via CTM.
Contact <CTM@@FreeBSD.org> for that.

What is CTM ?
-------------
CTM was originally "CVS Through eMail", but has since changed scope to be
much more general.
CTM is now meant to be the definitive way to make and apply a delta between
two versions of a directory tree.
There are two parts to this, making the delta and applying it.  These are two
entirely different things.  CTM concentrates the computation-burden on the
generation of the deltas, as a delta very often is applied more times than
it is made.  Second CTM tries to make the minimal size delta.

Why not use diff/patch ?
------------------------
Good question.  Primarily because diff and patch doesn't do their job very 
well.  They don't deal with binary files (in this case files with '\0' or 
'\0377' characters in them or files that doesn't end in '\n') which isn't
a big surprise:  they were made to deal with text-files only.  As a second
gripe, with patch you send the entire file to delete it.  Not particular
efficient.

So what does CTM do exactly ?
-----------------------------
CTM will produce a file, (a delta) containing the instructions and data needed
to take another copy of the tree from the old to the new status.  CTM means to
do this in the exact sense, and therefore the delta contains MD5 checksums to
verify that the tree it is applied to is indeed in the state CTM expects.

This means that if you have modified the tree locally, CTM might not be able
to upgrade your copy.

How do I make a CTM-delta ?
---------------------------

Read the source, and be prepared to have 2 copies of the tree; One is
the reference ("From") tree, and the other is the delta ("To") tree.
The mkCTM script will create the CTM diff of the differences between
the reference tree and the delta tree. A lot of scratch space is
required, and your machine will work hard.

How do I apply a CTM-delta ?
----------------------------
You pass it to the 'ctm' command.  You can pass a CTM-delta on stdin, or
you can give the filename as an argument.  If you do the latter, you make
life a lot easier for your self, since the program can accept gzip'ed files
and since it will not have to make a temporary copy of your file.  You can
specify multiple deltas at one time, they will be processed one at a time.

The ctm command runs in a number of passes.  It will process the entire
input file in each pass, before commencing with the next pass.

Pass 1 will validate that the input file is OK.  The syntax, the data and 
the global MD5 checksum will be checked.  If any of these fail, ctm will
never be able to do anything with the file, so it will simply reject it.

Pass 2 will validate that the directory tree is in the state expected by
the CTM-delta.  This is done by looking for files and directories which
should/should not exists and by checking the MD5 checksums of files.  

Pass 3 will actually apply the delta.

Should I delete the delta when I have applied it ?
--------------------------------------------------
No.  You might want to selectively reconstruct a file latter on.

Why is CTM not being maintained?
--------------------------------
Because CVSUP has improved on the concept quite a bit, and is now
the method of choice.

Poul-Henning
@


1.10
log
@Modernize my email address.
@
text
@d8 1
a8 1
# $FreeBSD$
@


1.10.24.1
log
@Switch importer
@
text
@d8 1
a8 1
# $FreeBSD: stable/7/usr.sbin/ctm/README 93151 2002-03-25 14:12:49Z phk $
@


1.10.14.1
log
@Switch importer
@
text
@d8 1
a8 1
# $FreeBSD: stable/6/usr.sbin/ctm/README 93151 2002-03-25 14:12:49Z phk $
@


1.10.42.1
log
@SVN rev 225736 on 2011-09-23 00:51:37Z by kensmith

Copy head to stable/9 as part of 9.0-RELEASE release cycle.

Approved by:	re (implicit)
@
text
@@


1.10.42.2
log
@## SVN ##
## SVN ## Exported commit - http://svnweb.freebsd.org/changeset/base/ 242902
## SVN ## CVS IS DEPRECATED: http://wiki.freebsd.org/CvsIsDeprecated
## SVN ##
## SVN ## ------------------------------------------------------------------------
## SVN ## r242902 | dteske | 2012-11-11 23:29:45 +0000 (Sun, 11 Nov 2012) | 10 lines
## SVN ##
## SVN ## Fix a regression introduced by SVN r211417 that saw the breakage of a feature
## SVN ## documented in usr.sbin/sysinstall/help/shortcuts.hlp (reproduced below):
## SVN ##
## SVN ## If /usr/sbin/sysinstall is linked to another filename, say
## SVN ## `/usr/local/bin/configPackages', then the basename will be used
## SVN ## as an implicit command name.
## SVN ##
## SVN ## Reviewed by:	adrian (co-mentor)
## SVN ## Approved by:	adrian (co-mentor)
## SVN ##
## SVN ## ------------------------------------------------------------------------
## SVN ##
@
text
@d8 1
a8 1
# $FreeBSD: stable/9/usr.sbin/ctm/README 93151 2002-03-25 14:12:49Z phk $
@


1.10.42.1.4.1
log
@SVN rev 239080 on 2012-08-05 23:54:33Z by kensmith

Copy stable/9 to releng/9.1 as part of the 9.1-RELEASE release process.

Approved by:	re (implicit)
@
text
@@


1.10.42.1.4.2
log
@Switch importer
@
text
@d8 1
a8 1
# $FreeBSD: releng/9.1/usr.sbin/ctm/README 93151 2002-03-25 14:12:49Z phk $
@


1.10.42.1.2.1
log
@SVN rev 227445 on 2011-11-11 04:20:22Z by kensmith

Copy stable/9 to releng/9.0 as part of the FreeBSD 9.0-RELEASE release
cycle.

Approved by:	re (implicit)
@
text
@@


1.10.42.1.2.2
log
@Switch importer
@
text
@d8 1
a8 1
# $FreeBSD: releng/9.0/usr.sbin/ctm/README 93151 2002-03-25 14:12:49Z phk $
@


1.10.40.1
log
@SVN rev 216618 on 2010-12-21 17:10:29Z by kensmith

Copy stable/7 to releng/7.4 in preparation for FreeBSD-7.4 release.

Approved by:	re (implicit)
@
text
@@


1.10.40.2
log
@Switch importer
@
text
@d8 1
a8 1
# $FreeBSD: releng/7.4/usr.sbin/ctm/README 93151 2002-03-25 14:12:49Z phk $
@


1.10.38.1
log
@SVN rev 203736 on 2010-02-10 00:26:20Z by kensmith

Copy stable/7 to releng/7.3 as part of the 7.3-RELEASE process.

Approved by:	re (implicit)
@
text
@@


1.10.36.1
log
@SVN rev 196045 on 2009-08-03 08:13:06Z by kensmith

Copy head to stable/8 as part of 8.0 Release cycle.

Approved by:	re (Implicit)
@
text
@@


1.10.36.2
log
@## SVN ##
## SVN ## Exported commit - http://svnweb.freebsd.org/changeset/base/ 242909
## SVN ## CVS IS DEPRECATED: http://wiki.freebsd.org/CvsIsDeprecated
## SVN ##
## SVN ## ------------------------------------------------------------------------
## SVN ## r242909 | dim | 2012-11-12 07:47:19 +0000 (Mon, 12 Nov 2012) | 20 lines
## SVN ##
## SVN ## MFC r242625:
## SVN ##
## SVN ## Remove duplicate const specifiers in many drivers (I hope I got all of
## SVN ## them, please let me know if not).  Most of these are of the form:
## SVN ##
## SVN ## static const struct bzzt_type {
## SVN ##       [...list of members...]
## SVN ## } const bzzt_devs[] = {
## SVN ##       [...list of initializers...]
## SVN ## };
## SVN ##
## SVN ## The second const is unnecessary, as arrays cannot be modified anyway,
## SVN ## and if the elements are const, the whole thing is const automatically
## SVN ## (e.g. it is placed in .rodata).
## SVN ##
## SVN ## I have verified this does not change the binary output of a full kernel
## SVN ## build (except for build timestamps embedded in the object files).
## SVN ##
## SVN ## Reviewed by:	yongari, marius
## SVN ##
## SVN ## ------------------------------------------------------------------------
## SVN ##
@
text
@d8 1
a8 1
# $FreeBSD: stable/8/usr.sbin/ctm/README 93151 2002-03-25 14:12:49Z phk $
@


1.10.36.1.8.1
log
@SVN rev 232438 on 2012-03-03 06:15:13Z by kensmith

Copy stable/8 to releng/8.3 as part of 8.3-RELEASE release cycle.

Approved by:	re (implicit)
@
text
@@


1.10.36.1.8.2
log
@Switch importer
@
text
@d8 1
a8 1
# $FreeBSD: releng/8.3/usr.sbin/ctm/README 93151 2002-03-25 14:12:49Z phk $
@


1.10.36.1.6.1
log
@SVN rev 216617 on 2010-12-21 17:09:25Z by kensmith

Copy stable/8 to releng/8.2 in preparation for FreeBSD-8.2 release.

Approved by:	re (implicit)
@
text
@@


1.10.36.1.4.1
log
@SVN rev 209145 on 2010-06-14 02:09:06Z by kensmith

Copy stable/8 to releng/8.1 in preparation for 8.1-RC1.

Approved by:	re (implicit)
@
text
@@


1.10.36.1.2.1
log
@SVN rev 198460 on 2009-10-25 01:10:29Z by kensmith

Copy stable/8 to releng/8.0 as part of 8.0-RELEASE release procedure.

Approved by:	re (implicit)
@
text
@@


1.10.34.1
log
@SVN rev 191087 on 2009-04-15 03:14:26Z by kensmith

Create releng/7.2 from stable/7 in preparation for 7.2-RELEASE.

Approved by:	re (implicit)
@
text
@@


1.10.32.1
log
@SVN rev 185281 on 2008-11-25 02:59:29Z by kensmith

Create releng/7.1 in preparation for moving into RC phase of 7.1 release
cycle.

Approved by:	re (implicit)
@
text
@@


1.10.30.1
log
@SVN rev 183531 on 2008-10-02 02:57:24Z by kensmith

Create releng/6.4 from stable/6 in preparation for 6.4-RC1.

Approved by:	re (implicit)
@
text
@@


1.9
log
@Correct the email address that folk are to bug if they need
help; also point them in the direction of the source, not
PHK (or any other human) if they need to make CTM deltas
of their own.
@
text
@d3 1
a3 1
# <phk@@login.dknet.dk> wrote this file.  As long as you retain this notice you
d8 1
a8 1
# $FreeBSD: src/usr.sbin/ctm/README,v 1.8 1999/08/28 01:15:58 peter Exp $
@


1.9.2.1
log
@Switch importer
@
text
@d8 1
a8 1
# $FreeBSD: stable/4/usr.sbin/ctm/README 53887 1999-11-29 17:58:58Z markm $
@


1.8
log
@$Id$ -> $FreeBSD$
@
text
@d8 1
a8 1
# $FreeBSD$
d14 1
a14 1
Contact <phk@@freefall.cdrom.com> for that.
d18 1
a18 1
CTM was originally "Cvs Through eMail", but has since changed scope to be
d48 6
a53 3
Don't.  Send me email before you even try.  This is yet not quite as trivial
as I would like.  This is not to discourage you from using CTM, it is merely
to warn you that it is slightly tedious and takes much diskspace.
d80 4
a83 19
What features are are planned ?
-------------------------------
This list isn't exhaustive, and it isn't sorted in priority.
	Reconstruct subset of tree.
	Make tar-copy of things which will be affected.
	Verify.
	Internal editor instead of ed(1)
	Support for mode
	Support for uid/gid
	Support for hardlinks
	Support for symlinks

Isn't this a bit thin yet ?
---------------------------
Yes.

Can I say something ?
---------------------
Yes, email me: <phk@@freefall.cdrom.com>
@


1.7
log
@Spelling/typo fixes: (proccessed, og).
@
text
@d8 1
a8 1
# $Id: README,v 1.6 1997/02/22 16:05:15 peter Exp $
@


1.7.2.1
log
@$Id$ -> $FreeBSD$
@
text
@d8 1
a8 1
# $FreeBSD$
@


1.6
log
@Revert $FreeBSD$ to $Id$
@
text
@d8 1
a8 1
# $Id$
d24 1
a24 1
generation og the deltas, as a delta very often is applied more times than
d58 1
a58 1
specify multiple deltas at one time, they will be proccessed one at a time.
@


1.5
log
@Make the long-awaited change from $Id$ to $FreeBSD$

This will make a number of things easier in the future, as well as (finally!)
avoiding the Id-smashing problem which has plagued developers for so long.

Boy, I'm glad we're not using sup anymore.  This update would have been
insane otherwise.
@
text
@d8 1
a8 1
# $FreeBSD$
@


1.4
log
@Various cleanup and fixes.
@
text
@d8 1
a8 1
# $Id$
@


1.4.6.1
log
@$Id$ -> $FreeBSD$
@
text
@d8 1
a8 1
# $FreeBSD$
@


1.4.8.1
log
@MFC: doc changes, new rate-limiting inetd(8), lots of minor cosmetic tweaks.
@
text
@d8 1
a8 1
# $Id: README,v 1.4 1994/09/22 02:49:07 phk Exp $
d24 1
a24 1
generation of the deltas, as a delta very often is applied more times than
d58 1
a58 1
specify multiple deltas at one time, they will be processed one at a time.
@


1.4.8.2
log
@$Id$ -> $FreeBSD$
@
text
@d8 1
a8 1
# $FreeBSD$
@


1.3
log
@The next batch of refinements.  Now it no longer needs to call on ed(1) to
fix our files, it has a builtin "diff -n" editor.
@
text
@@


1.2
log
@A bunch of improvements.  Still far to go.
@
text
@@


1.1
log
@Initial revision
@
text
@@


1.1.1.1
log
@This is the present state of CTM version 2.  Please do not ask for 
subscriptions yet.  Wait for the announcement.

CTM is my humble attempt to get -current out to people beyond TCP/IP 
connections.  This is for people with dial-up connections and such.

CTM can make a delta from one version to another of a source-tree, in 
a efficient and verified way.  Even if there are binary files in the
tree.  It will even try to make the delta as small as possible.

It is OK with me if you yell "Bloating!" but I'll just forward your email
to some of the happy customers from CTM version 1, and let them tell you
what they think.

I will not put ctm into "make world" yet.  For now it is just the logical
way to get the sources out to people who helps me test this.

Poul-Henning

@
text
@@
