Change 16428 by jhi@alpha on 2002/05/06 12:12:59

        Ultimate discouragement for the old tools, from Andreas.

Affected files ...

.... //depot/perl/MANIFEST#877 edit
.... //depot/perl/Porting/p4d2p#3 delete
.... //depot/perl/Porting/p4desc#8 delete
.... //depot/perl/Porting/repository.pod#6 edit

Differences ...

==== //depot/perl/MANIFEST#877 (text) ====
Index: perl/MANIFEST
--- perl/MANIFEST#876~16419~    Sun May  5 15:15:48 2002
+++ perl/MANIFEST       Mon May  6 05:12:59 2002
@@ -2206,8 +2206,6 @@
 Porting/genlog         Generate formatted changelogs by querying p4d
 Porting/Glossary       Glossary of config.sh variables
 Porting/makerel                Release making utility
-Porting/p4d2p          Generate standard patches from p4 diffs
-Porting/p4desc         Smarter 'p4 describe', outputs diffs for new files
 Porting/p4genpatch     Obsoletes both p4desc and p4d2p
 Porting/patching.pod   How to report changes made to Perl
 Porting/patchls                Flexible patch file listing utility

==== //depot/perl/Porting/repository.pod#6 (text) ====
Index: perl/Porting/repository.pod
--- perl/Porting/repository.pod#5~11447~        Sun Jul 22 21:57:49 2001
+++ perl/Porting/repository.pod Mon May  6 05:12:59 2002
@@ -328,9 +328,9 @@
 
 Generating a patch for change#42 is done as follows:
 
-    % p4 describe -du 42 | p4desc | p4d2p > change-42.patch
+    % p4genpatch 42 > change-42.patch
 
-F<p4desc> and F<>p4d2p> are to be found in //depot/perl/Porting/.
+F<p4genpatch> is to be found in //depot/perl/Porting/.
 
 The usual routine to apply a patch is
 
@@ -356,7 +356,7 @@
     % p4 describe -du 12345 # show change 12345
 
 Note: the output of "p4 describe" is not in proper diff format, use
-the F<Porting/p4d2p> to convert.
+the F<Porting/p4genpatch> to get a diff-compatible format.
 
     % p4 diff -se ./...     # have I modified something but forgotten
                             # to "p4 edit", easy faux pas with autogenerated
End of Patch.

Reply via email to