Re: Best practice to patch a existing module written by others

From: "Tom" <chi.lun@xxxxxxxxx>
Date: 12 Oct 2005 00:38:56 -0700

Thanks a lot.

The links you post are very helpful.
Besides, I search for the mailing archive but could not find my 1st
posting. I think there is an error occured last time.

I requested again and then this new message appear in the mailing list.
:)

.

References:
- Best practice to patch a existing module written by others
  - From: Tom
- Re: Best practice to patch a existing module written by others
  - From: brian d foy
- Re: Best practice to patch a existing module written by others
  - From: Tom
- Re: Best practice to patch a existing module written by others
  - From: Randy Kobes

Prev by Date: Re: default location for apache2.pm
Next by Date: Perl DBI ODBC
Previous by thread: Re: Best practice to patch a existing module written by others
Next by thread: Re: Can't locate warnings.pm in @INC
Index(es):
- Date
- Thread