[ic] Submitting patches (was: MaxQuantityField, cart.pmmodification; to allow for stock at multiple locations)

John1 list_subscriber at yahoo.co.uk
Tue May 4 17:03:08 EDT 2004

On Monday, May 03, 2004 11:10 PM, kevin at cursor.biz wrote:

>> Can you point me in the direction of a "Submitting a patch - How to"?
>> Do I need to install CVS?  I don't expect that I will be submitting
>> many patches as my Perl isn't up to much, so if there is a way I can
>> submit a patch without installing CVS that would be great.
> You don't need to use CVS unless you want to get the latest version
> from the repository.  You won't have write (commit) access to the
> repository by default.
> Assuming you still have a copy of the original file, you can create
> a patch file with the following command:
>     diff -c foo.pm.orig foo.pm > foo.pm.patch
> If you're using CVS then you can compare your file with the one in
> the CVS repository as follows:
>     cvs diff -c foo.pm > foo.pm.patch
> Once you have a patch file, you can email it to this mail list, or
> the core list, and it will be picked up from there.  Please state the
> original file's version number when submitting a patch.
> Also, don't expect the patch, if accepted, to necessarily appear in
> the next release; Depending upon the change, the patch may be applied
> to the development source, instead of to the stable branch, in which
> case it won't be seen until the next major version.  Of course, if
> the patch is deemed to have zero impact on current setups and is also
> deemed to be stable then it may be included in the next stable
> release.
> You, of course, are free to re-apply your patch to every upgrade you
> perform until it's included as standard.
Thank you Kevin!  And I now see from a few web searches that this is a
common way of submitting patches.  I also see that the *nix "patch" command
is commonly used to apply patches produced with diff.  Learning something
new every day :-)

More information about the interchange-users mailing list