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
signature.asc
Description: OpenPGP digital signature
