This commit was generated by cvs2svn to compensate for changes in r128266,

which included commits to RCS files with non-trunk default branches.

1 files changed, 3 insertions, 3 deletions

diff --git a/contrib/cvs/src/classify.c b/contrib/cvs/src/classify.c
index 285153c..7ce8235 100644
--- a/contrib/cvs/src/classify.c
+++ b/contrib/cvs/src/classify.c
@@ -266,7 +266,7 @@ Classify_File (finfo, tag, date, options, force_tag_match, aflag, versp,
 		 * There is no user file, so note that it was lost and
 		 * extract a new version
 		 */
-		/* Comparing the command_name against "update", in
+		/* Comparing the cvs_cmd_name against "update", in
 		   addition to being an ugly way to operate, means
 		   that this message does not get printed by the
 		   server.  That might be considered just a straight
@@ -274,7 +274,7 @@ Classify_File (finfo, tag, date, options, force_tag_match, aflag, versp,
 		   gets hit when a patch fails and the client fetches
 		   a file.  I'm not sure there is currently any way
 		   for the server to distinguish those two cases.  */
-		if (strcmp (command_name, "update") == 0)
+		if (strcmp (cvs_cmd_name, "update") == 0)
 		    if (!really_quiet)
 			error (0, 0, "warning: %s was lost", finfo->fullname);
 		ret = T_CHECKOUT;
@@ -344,7 +344,7 @@ Classify_File (finfo, tag, date, options, force_tag_match, aflag, versp,
 
 		/* See comment at other "update" compare, for more
 		   thoughts on this comparison.  */
-		if (strcmp (command_name, "update") == 0)
+		if (strcmp (cvs_cmd_name, "update") == 0)
 		    if (!really_quiet)
 			error (0, 0, "warning: %s was lost", finfo->fullname);
 		ret = T_CHECKOUT;