You are viewing a plain text version of this content. The canonical link for it is here.
Posted to test-commits@perl.apache.org by ge...@apache.org on 2006/02/22 17:04:58 UTC

svn commit: r379805 - /perl/Apache-Test/trunk/RELEASE

Author: geoff
Date: Wed Feb 22 08:04:56 2006
New Revision: 379805

URL: http://svn.apache.org/viewcvs?rev=379805&view=rev
Log:
update replace command so it fits on one line

Modified:
    perl/Apache-Test/trunk/RELEASE

Modified: perl/Apache-Test/trunk/RELEASE
URL: http://svn.apache.org/viewcvs/perl/Apache-Test/trunk/RELEASE?rev=379805&r1=379804&r2=379805&view=diff
==============================================================================
--- perl/Apache-Test/trunk/RELEASE (original)
+++ perl/Apache-Test/trunk/RELEASE Wed Feb 22 08:04:56 2006
@@ -77,9 +77,7 @@
   c. bump up version numbers in this file to make it easier to do the
      next release.
 
-   perl -pi -e 's/\.31/.32/g' RELEASE
-   perl -pi -e 's/\.30/.31/g' RELEASE
-   perl -pi -e 's/\.29/.30/g' RELEASE
+     $ perl -pi -e 's/\.31/.32/g; s/\.30/\.31/g; s/\.29/\.30/g' RELEASE
 
      now reload this file and bump up the last number of the first
      command.



Re: svn commit: r379805 - /perl/Apache-Test/trunk/RELEASE

Posted by "Philippe M. Chiasson" <go...@ectoplasm.org>.
Geoffrey Young wrote:
>>>-   perl -pi -e 's/\.31/.32/g' RELEASE
>>>-   perl -pi -e 's/\.30/.31/g' RELEASE
>>>-   perl -pi -e 's/\.29/.30/g' RELEASE
>>>+     $ perl -pi -e 's/\.31/.32/g; s/\.30/\.31/g; s/\.29/\.30/g' RELEASE
>>>
>>>     now reload this file and bump up the last number of the first
>>>     command.
>>
>>
>>With that change, the sentence that follows doesn't make much sense anymore.
>>"the last number of the first command"
> 
> well, it's the last number of the first s/// command, maybe? :)
> 
> really, I don't care what it says, so feel free to adjust the language so it
> feels right to you.  my biggest gripe was after the running the first
> one-liner you couldn't open RELEASE back up and run the next one and have it
> be right, which is why I suspect the RELEASE file numbers were mucked up
> this time around.  so as long as _that_ isn't a problem...

Taken care of in r382226. There is no more need for any explanation, as the
one-liner now doesn't need to self-update anymore.

--------------------------------------------------------------------------------
Philippe M. Chiasson m/gozer\@(apache|cpan|ectoplasm)\.org/ GPG KeyID : 88C3A5A5
http://gozer.ectoplasm.org/     F9BF E0C2 480E 7680 1AE5 3631 CB32 A107 88C3A5A5

Re: svn commit: r379805 - /perl/Apache-Test/trunk/RELEASE

Posted by Geoffrey Young <ge...@modperlcookbook.org>.
>>-   perl -pi -e 's/\.31/.32/g' RELEASE
>>-   perl -pi -e 's/\.30/.31/g' RELEASE
>>-   perl -pi -e 's/\.29/.30/g' RELEASE
>>+     $ perl -pi -e 's/\.31/.32/g; s/\.30/\.31/g; s/\.29/\.30/g' RELEASE
>> 
>>      now reload this file and bump up the last number of the first
>>      command.
> 
> 
> With that change, the sentence that follows doesn't make much sense anymore.
> "the last number of the first command"

well, it's the last number of the first s/// command, maybe? :)

really, I don't care what it says, so feel free to adjust the language so it
feels right to you.  my biggest gripe was after the running the first
one-liner you couldn't open RELEASE back up and run the next one and have it
be right, which is why I suspect the RELEASE file numbers were mucked up
this time around.  so as long as _that_ isn't a problem...

:)

--Geoff