Subject: bin/12785: "man cvs" does not describe the 'P' update type
To: None <gnats-bugs@gnats.netbsd.org>
From: Robert Elz <kre@munnari.OZ.AU>
List: netbsd-bugs
Date: 04/30/2001 00:04:26
	Note: There was a bad value `docbug' for the field `>Class:'.
	It was set to the default value of `sw-bug'.


>Number:         12785
>Category:       bin
>Synopsis:       "man cvs" does not describe the 'P' update type
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    bin-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sun Apr 29 10:05:00 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     Robert Elz
>Release:        All since cvs was integrated I believe (including -current)
>Organization:
	University of Melbourne
>Environment:
	
System: NetBSD brandenburg.cs.mu.OZ.AU 1.5_BETA NetBSD 1.5_BETA (BRANDENBURG) #4: Mon Dec 4 17:01:12 EST 2000 kre@brandenburg.cs.mu.OZ.AU:/usr/src/sys/arch/i386/compile/BRANDENBURG i386


>Description:
	The man page for cvs describes the output that can appear from
	the "cvs update" command.   It describes U A R M C and ?.
	It doesn't describe 'P' - yet 'P' is one of the more common
	outputs.
>How-To-Repeat:
	"cvs update" (with -d and -P of course...)
	man cvs
	compare the differences...
>Fix:
	Add the appropriate text (I don't know for sure, I'm guessing
	that 'P' == 'U' for anything that really matters, but that the
	way the update is transmitted from the cvs server to client is
	perhaps different?   'P' might be "sent a patch" and 'U' "sent the
	whole file"?

	I'm not sure why that difference is relevant (assuming this is what
	it in fact is), but if it is, shouldn't there also be equivalents
	for 'M' and 'C' to indicate whether just a patch or the whole file
	was sent (before local changes were merged, or conflicts were
	discovered) ??

	And it would be real nice for the output from CVS to distinguish
	between "local changes, but nothing altered in the reppository"
	and "changes from the repository merged with local changes without
	conflict" ... but I can't ask for that here, as that would be
	putting a software enhancement request in a doc-bug PR, and that
	would seriously be bad juju...
>Release-Note:
>Audit-Trail:
>Unformatted: