Re: patch should assume $PATCH_GET=0 when $PATCH_GET is unset

[Chip Salzenberg]

According to Paul Eggert:
> Chip Salzenberg <address@hidden> writes:
> > It's remarkably intrusive, almost aggressively hostile, for a new
> > version of patch to assume it knows about source control and try to
> > do source control activities without express request.
> 
> I agree it's an undesirable behavior, but it's not a new behavior.
> That behavior has been present in 'patch' since 1984, the year that
> Larry Wall first wrote 'patch'.

Do tell.  In that case, I'll limit my complaint to patch's new
assumption (this part *is* new, right?) that the current Perforce
settings ($P4PORT, etc.)  are relevant to files being patched, even
though said files fall outside all Perforce working areas.
-- 
Chip Salzenberg               - a.k.a. -               <address@hidden>
"I wanted to play hopscotch with the impenetrable mystery of existence,
    but he stepped in a wormhole and had to go in early."  // MST3K