Emiliano wrote:
> 
> Ferenc Engard wrote:
> 
> > I know it is a shame that I use linux since 6-7 years and never posted a
> > patch, but that's the fact. :-/
> >
> > So, here are the diffs which can patch the jan.15. cvs, but I didn't
> > make it that you can patch it from the CVS rootdir.
> 
> That would be mostly preferable, though.

Yes, I know it, that's why I mentioned it, and also that this is my
first  patch what I send to another person. I hope that it helped,
anyway...

> 
> > The access.c should be patched in lib/src/, the others should be patched
> > in php4/.
> 
> You don't need to make separate diffs for eac file, BTW.

Well, actually, somebody has sent the patches to the list, I just
applied to the CVS (and applied by hand the one what was rejected), and
thus knew that the CVS can be patched with them. (And of course made a
new patch where the original was rejected.)

> > Anyway, nowadays I face with signs like win*: ordinary programs do nasty
> > things, and I can't find the problem's origin. For example, the
> > php4/mgd_event.h file was patched without a word, without creating .orig
> > file, although the patch looks like the other patches, and the command I
> > patched with was the same. :-O
> 
> I'm not sure right now, but if a patch succeeds I don't think it creates
> a .orig. Right?

No, the other patches created .orig. :-O

> > (Another, offtopic: When I tried to copy the access.c.diff from one
> > linux to the other linux through smbfs for emailing it, the 'cp' said an
> > error message 'cannot create regular file'. If I copied to the same dir,
> > but on another name, and renamed on the dest host, after that trying
> > 'cp' again was successful. :-O )
> 
> That could be samba. Could well be that it was doing something funky
> with extension guarding. On the dest host, from the command line, you
> can do what you want of course.

Yes, I just thought that maybe filesystem inconsistency... Hm.

Bye:
Circum


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to