File: README

package info (click to toggle)
curves 0.8.7
  • links: PTS
  • area: main
  • in suites: slink
  • size: 704 kB
  • ctags: 1,001
  • sloc: cpp: 6,197; ansic: 519; makefile: 270; sh: 192; fortran: 149
file content (44 lines) | stat: -rw-r--r-- 1,749 bytes parent folder | download | duplicates (3)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
  ================
  CVS-Patch README
  ================

cvs-1.10.1-statushash

	This patch adds the status hashing feature to cvs which
	improves the performance of the cvs status command when using
	the client/server mode.  Normally, the client sends to the
	server the contents of any file that might have been
	modified.  This patch adds the -H option to cvs status so that
	only a hash of the file is sent.  This is a very effective
	performance improvement when low-bandwidth connections between
	the client and the server.

	status -H
		Use file content hashing to reduce the traffic to the
		server.
	status -e
		Emit compressed status report for easier machine
		parsing.  Appears to be about a 20% savings on
		transmission bytes when compressed woth -z9. 
	status -M
		Request status for modified or potentially modified
		files only.  This is used by an optimized update
		command to determine the smallest set of sources that
		need to be transmitted to the server.


----- NOTES

- Create Rcs-merge response that is similar to Rcs-diff but sends both
  the base revision and the patch to the latest tip revision. 
- Perform the same hook as Rcs-diff, configure the update_?? call with
  an enum to indicate that we'll read an extra file buffer, the base
  revision.  This will come after the patch since this leave the patch
  structure intact and will permit us to drop the base revision
  (size < 0?) if we know that the user has one intact.
- At the bottom of the update call, we will perform the
  rcs-change-text to recover the latest tip revision and then call the
  RCS_merge like function to perform the merge.
- Our history will be similar to 'P' for patch since we don't have any
  way to know if it was successful.
- Cake.