Waynn Lue wrote:
> Yeah, that's why I was hoping to maintain a separate install, since it
> would be easier to diff the patches.
>
> Shawn: Thanks for the suggestion to extend, I only wanted to make
> small changes to an existing function though, so it's harder to do it
> that way. My other though
Waynn Lue wrote:
> Yeah, that's why I was hoping to maintain a separate install, since it
> would be easier to diff the patches.
>
> Shawn: Thanks for the suggestion to extend, I only wanted to make
> small changes to an existing function though, so it's harder to do it
> that way. My other thought
Yeah, that's why I was hoping to maintain a separate install, since it
would be easier to diff the patches.
Shawn: Thanks for the suggestion to extend, I only wanted to make
small changes to an existing function though, so it's harder to do it
that way. My other thought was to refactor the underly
Waynn Lue wrote:
> I wanted to makes some local edits to a PEAR package that I downloaded in
> order to build some custom functionality into it. What's the best way to
> manage this process to ensure that I don't accidentally blow away any
> changes if I update the package? Should I just copy the
Waynn Lue wrote:
> I wanted to makes some local edits to a PEAR package that I downloaded in
> order to build some custom functionality into it. What's the best way to
> manage this process to ensure that I don't accidentally blow away any
> changes if I update the package? Should I just copy the
5 matches
Mail list logo
