Use -P for updates and checkouts

git-svn-id: https://svn.dealii.org/trunk@5494 0785d39b-7218-0410-832d-ea1e28bc413d

diff --git a/deal.II/doc/RELEASE/tasks b/deal.II/doc/RELEASE/tasks
index 113da91dd99bf04ef01a8ee5d1f39169dfb38472..d2bd3eccb776ece3ad1a8a0c888e19c1ccdc3d4a 100644 (file)
--- a/deal.II/doc/RELEASE/tasks
+++ b/deal.II/doc/RELEASE/tasks
@@ -1,14 +1,14 @@
 This file is internal information only. It lists the steps to be done
 when a new release shall be issued:
 
-0/ cvs update -d
+0/ cvs update -d -P
 
 1/ if a x.y.0 release, create a branch:
        call common/scripts/cvs-create-branch <x> <y>
 
-2/  cvs update -r Branch-<x>-<y>
+2/  cvs update -P -r Branch-<x>-<y>
        or
-       cvs checkout -r Branch-<x>-<y> deal.II
+       cvs checkout -P -r Branch-<x>-<y> deal.II
 
 3/ change the content of the `Version' file on both HEAD and branch
 
@@ -29,7 +29,7 @@ when a new release shall be issued:
 
 10/ tell your friends to tag their programs
 
-11/ cvs export -r Version-x-y-z and form a tarball of that
+11/ cvs export -P -r Version-x-y-z and form a tarball of that
 
 12/ put it on the web server