Hi,
"Unless I remember my own experience incorrectly, it already is fixed.
For a long while, actually. It's called the '-p' option of patch.
"cvs diff" output usually needs "patch -p0". It's the change in
default status of -p, going from "-p0" to "-p infinity" to suit POSIX,
which broke this particular usage of patch. Not CVS."
That would mean i can use cvs diff for patches??? (seems to be easier to
me...)
Greetings, Patty
Pattrick Hueper wrote:
> Hi again,
>
> actually, if i use "patch -p0 ..." it accepts the patch.
>
> Greetings, Patty
>
> Pattrick Hueper wrote:
>
>> Hi,
>>
>>>>
>>>> That being said,
>>>> cvs diff -u
>>>> creates patches that the patch program does not like. It is better
>>>> to have two snapshots of the source code and use diff -u or diff
>>>> -urN to create the patch file.
>>>
>>>
>>>
>>
>> uups, didnt know that, i only tried my file with kompare, and that
>> worked...
>>
>> whats the procedure to create a good patch file? If i create a new
>> snapshot, update it and run diff -urN, it of course reports all the
>> files generated by the compile, and it also reports differences in
>> CVS/... files. Is there any way around that?
>>
>> Patty
>> _______________________________________________
>> H2200-port mailing list
>> H2200-port@handhelds.org
>> https://handhelds.org/mailman/listinfo/h2200-port
>>
>>
>
>
Received on Mon Mar 01 16:56:58 2004
This archive was generated by hypermail 2.1.8 : Tue May 04 2004 - 09:41:46 EDT