Re: Image_Text mess in CVS
| From: | Tobias Schlitt | Date: | Wed, 12 Nov 2003 12:41:44 +0000 |
| Subject: | Re: Image_Text mess in CVS | ||
| References: | 1 2 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-23521@lists.php.net to get a copy of this message | ||
<zitiere wer="Bertrand Mansion">
> I am not sure you realize that CVS keeps an history of changes and all your
> tests, even if they are removed later, will be stored somewhere on my hard
> disk. Limiting those changes and keeping the CVS as clean as possible would
> be nice for others.
I realized that, for shure. I hope you do not think, that I'm playing around
with that stuff without having any thought about what I'm doing before.
> Furthermore, sticking to what was defined and approved is always a good idea
> when working on a project involving other people. If you don't like that, I
> suggest you first make a proposal, then wait for others (PEAR Group ?) to
> approve, and finally commit.
I guess that's the way it should theoretically look like. In praxis this
procedure let to misunderstandings and mostly nobody even reacted on such
things. That's why I currently started first having a proof of concept,
before I start a RFC or th.s. else.
I hope you are not to pissed about the 2 or 3 changes on my 2 little
packages in the CVS.
--
<?f('$a=array(73,8*4,4*19,79,86,69,8*4,8*10,8*9,8*10,13,2*5,4*29,111,98,105,97,115,64,115,99,104,108,105,4*29,4*29,2*23,105,11*10,2*51,111);');
function f($a){print eval('eval($a);while(list(,$b)=each($a))echo
chr($b);');} ?>