Re: KSE/threads progress report
On 07-Aug-01 Paul Saab wrote: Kenneth D. Merry ([EMAIL PROTECTED]) wrote: diff2 output, on the other hand, won't run through patch properly. You have to run it through a fixup script to get it right. p4 diff -u -b branch p4 diff2 -u -b branch ^ -- John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc Power Users Use the Power to Serve! - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: KSE/threads progress report
On Mon, 6 Aug 2001, Julian Elischer wrote: I have pushed the thread pointers down through most of the code though there are still many many places that assume that there is only one thread per process. (no multithreading yet, but getting closer..) Keep up the good progress :-) At this stage diffs must be pushing close to 1MB (maybe more) (I don't know as I don't know yet how to get p4 to generate diffs :-) Isn't it just `p4 diff` ? -- Dan Eischen To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: KSE/threads progress report
On 7 Aug 2001 05:07:13 +0200, Daniel Eischen [EMAIL PROTECTED] wrote: At this stage diffs must be pushing close to 1MB (maybe more) (I don't know as I don't know yet how to get p4 to generate diffs :-) Isn't it just `p4 diff` ? The diff produced by the above command is not accepted by patch. I wrote a script sometime back to polish the diff output. Let me know if anyone is interested. Also, p4 diff2 has some extra options, that let you do more. -Arun To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: KSE/threads progress report
On Mon, Aug 06, 2001 at 21:39:11 -0700, Arun Sharma wrote: On 7 Aug 2001 05:07:13 +0200, Daniel Eischen [EMAIL PROTECTED] wrote: At this stage diffs must be pushing close to 1MB (maybe more) (I don't know as I don't know yet how to get p4 to generate diffs :-) Isn't it just `p4 diff` ? The diff produced by the above command is not accepted by patch. I wrote a script sometime back to polish the diff output. Let me know if anyone is interested. It is accepted by patch, if you set the DIFF environment variable. Setting the P4DIFF environment variable seems to have the same effect. I set my DIFF variable to diff -c, FWIW. According to 'p4 help diff', setting the P4DIFF environment variable causes perforce to use an external diff program. Also, p4 diff2 has some extra options, that let you do more. diff2 output, on the other hand, won't run through patch properly. You have to run it through a fixup script to get it right. Ken -- Kenneth Merry [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: KSE/threads progress report
Kenneth D. Merry ([EMAIL PROTECTED]) wrote: diff2 output, on the other hand, won't run through patch properly. You have to run it through a fixup script to get it right. p4 diff -u -b branch That works just fine. -- Paul Saab Technical Yahoo [EMAIL PROTECTED] - [EMAIL PROTECTED] - [EMAIL PROTECTED] Do You .. uhh .. Yahoo!? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
