Re: [ID 20000120.001] Diff to add print formatting to debugger

[sthoenna@efn.org (Yitzchak Scott-Thoennes)]

In article <20000120161815.A29781@monk.mps.ohio-state.edu>,
Ilya Zakharevich <ilya@math.ohio-state.edu> wrote:
>On Thu, Jan 20, 2000 at 02:13:51PM -0700, Tom Christiansen wrote:
>> >a) If you want to send patches, use diff -pu or diff -p.
>> 
>> Why would you use -p for Perl code?
>
>Because it makes it easier to read patches.  Why else?
>
>>     % man 1 diff
>>     ...
>> 	   -p     Show which C function each change is in.
>> 
>> Also, -p isn't even in POSIX.2, so I don't know how you can expect people
>> to have it.
>
>Why is it important "how do I expect" things?  What is important is
>that people have it.  Though mentioning -c for a fallback would be
>nice indeed...

perldoc perlhack:
       Always submit patches to perl5-porters@perl.org.  This
       lets other porters review your patch, which catches a
       surprising number of errors in patches.  Either use the
       diff program (available in source code form from
       ftp://ftp.gnu.org/pub/gnu/), or use Johan Vromans'
       makepatch (available from CPAN/authors/id/JV/).  Unified
       diffs are preferred, but context diffs are accepted.  Do
       not send RCS-style diffs or diffs without context lines.

---

References to:

Tom Christiansen <tchrist@chthon.perl.com>
Ilya Zakharevich <ilya@math.ohio-state.edu>

---

[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index][Thread Index][Top&Search][Original]

---