From 3ed1f7ea58a26274ca25e065eea5ecf92d5fbc9c Mon Sep 17 00:00:00 2001 From: Nik Clayton Date: Wed, 11 Jul 2001 14:08:50 +0000 Subject: [PATCH] Favour over when talking about CVS subcommands. PR: docs/28731 Submitted by: Giorgos Keramidas --- .../articles/committers-guide/article.sgml | 42 +++++++++---------- 1 file changed, 21 insertions(+), 21 deletions(-) diff --git a/en_US.ISO8859-1/articles/committers-guide/article.sgml b/en_US.ISO8859-1/articles/committers-guide/article.sgml index 6865c416cb..4995e4d784 100644 --- a/en_US.ISO8859-1/articles/committers-guide/article.sgml +++ b/en_US.ISO8859-1/articles/committers-guide/article.sgml @@ -19,7 +19,7 @@ - $FreeBSD: doc/en_US.ISO8859-1/articles/committers-guide/article.sgml,v 1.74 2001/07/08 01:17:53 dd Exp $ + $FreeBSD: doc/en_US.ISO8859-1/articles/committers-guide/article.sgml,v 1.75 2001/07/11 13:22:17 nik Exp $ 1999 @@ -123,7 +123,7 @@ Note that when you use CVS on freefall, you should set your umask to 2, - as well as setting the CVSUMASK environment + as well as setting the CVSUMASK environment variable to 2. This ensures that any new files created by cvs add will have the correct permissions. If you add a file or directory and discover that the @@ -165,8 +165,8 @@ - Check out a module with the co or - checkout command. + Check out a module with the co or + checkout command. &prompt.user; cvs checkout shazam @@ -306,7 +306,7 @@ Check the status of checked-out files with the - status command. + status command. &prompt.user; cvs status shazam @@ -358,7 +358,7 @@ Once you've checked something out, update it with the - update command. + update command. &prompt.user; cvs update shazam @@ -370,7 +370,7 @@ stuff is going on. Useful options, in addition to those listed above for - checkout: + checkout: @@ -519,16 +519,16 @@ You'll almost certainly get a conflict because - of the $Id: article.sgml,v 1.75 2001-07-11 13:22:17 nik Exp $ (or in FreeBSD's case, + of the $Id: article.sgml,v 1.76 2001-07-11 14:08:50 nik Exp $ (or in FreeBSD's case, $FreeBSD$) lines, so you'll have to edit the file to resolve the conflict (remove the marker lines and - the second $Id: article.sgml,v 1.75 2001-07-11 13:22:17 nik Exp $ line, leaving the original - $Id: article.sgml,v 1.75 2001-07-11 13:22:17 nik Exp $ line intact). + the second $Id: article.sgml,v 1.76 2001-07-11 14:08:50 nik Exp $ line, leaving the original + $Id: article.sgml,v 1.76 2001-07-11 14:08:50 nik Exp $ line intact). View differences between the local version and the - repository version with the diff + repository version with the diff command. &prompt.user; cvs diff shazam @@ -569,7 +569,7 @@ You can also diff against a different version than the one you checked out by specifying a version with or as in - checkout or update, + checkout or update, or even view the diffs between two arbitrary versions (with no regard for what you have locally) by specifying two versions with or @@ -577,7 +577,7 @@ - View log entries with the log + View log entries with the log command. &prompt.user; cvs log shazam @@ -595,15 +595,15 @@ If shazam is a directory, then the log information described above is printed for each file in the directory in turn. Unless you give the to - log, the log for all subdirectories of + log, the log for all subdirectories of shazam is printed too, in a recursive manner. - Use the log command to view the history of + Use the log command to view the history of one or more files, as it's stored in the CVS repository. You can even use it to view the log message of a specific revision, if you add the to the - log command: + log command: &prompt.user; cvs log -r1.2 shazam @@ -615,7 +615,7 @@ - See who did what with the annotate command. + See who did what with the annotate command. This command shows you each line of the specified file or files, along with which user most recently changed that line. @@ -624,7 +624,7 @@ - Add new files with the add command. + Add new files with the add command. Create the file, cvs add it, then cvs commit it. @@ -635,15 +635,15 @@ - Remove obsolete files with the remove command. + Remove obsolete files with the remove command. Remove the file, then cvs rm it, then cvs commit it. - Commit with the commit or - checkin command. + Commit with the commit or + checkin command. Useful <command>cvs commit</command> options