Justin J <firstname.lastname@example.org>
Subject: Re: v6.2.2 Released
In-Reply-To: Re: v6.2.2 Released
Date: March 29th 2013
On Mar 29, 2013, at 3:55 PM, Mary Ann Kelley <email@example.com> wrote: > Guess I better upgrade then. Don't want to lose subscribers because of a bug. Does the whole thing need to be upgraded or can I just replace a single file to fix that issue?
I highly discourage "upgrading" by manually replacing single files - if you look at the changes between v6.2.1 and v6.2.2, you'll see it spans multiple files:
(Showing 22 changed files with 1,233 additions and 497 deletions.)
I don't put together patch files for upgrades, or have instructions on how to apply them. It's best to just upgrade normally. It should be relatively easy.
<< Previous: Re: v6.2.2 Released
| Archive Index |
Next: Re: v6.2.2 Released >>
This mailing list is to discuss the nerdy programming development of Dada Mail -
If you are just looking for support Dada Mail, consult the message boards at:
To post to this list, send a message to:
All subscribers of this list may post to the list itself.
Some on topic... topics include:
At the moment, there aren't many people with CVS access for Dada Mail - if you would like CVS access, please first talk about the changes you propose and how it will affect the program. If the idea is sound and agreed upon, the change will be comitted. A good track record of this will allow you to have CVS access. Some reasons that patches will not be accepted is if the patch breaks compatibility with a previous version of the program, the patch is too centric to your own problem or the patch simply isn't very good.
Please, please please familiarize yourself with the documentation at:
Since no one wants to answer the same question twice.
Another sneaky reason for this mailing list is to test out the discussion list capabilities of Dada Mail, since Dada Mail is used for the mailing list itself.
NOTE - because of this, there may be times that this list will be somewhat broken. Although we're not planning on breaking the program by using it, we're giving you the heads up that this may well happen anyways.