Hi Matt,
Not a big deal, but yes it's not a good practice and I was corrected many times
at my own beginning, that why I remember it well :o)
Actually when it's a different subject, for the sake of clairity you should open a new thread by creating an entirely new message
and not responding to an existing one. Because these last one contains information in its header which will hook it on the thread it
belongs
Thanks to care
Jacques
From: "Matt Warnock" <[email protected]>
Hmm. I usually just reply to an existing thread, but change the subject
line to create a new thread. It sounds from your comment like that may
not be good practice. Is there some thread identification code in the
header, usually invisible in mail clients, that I was not aware of?
If so, my apologies to everyone. I usually read this in Evolution on
Ubuntu, and was not aware of the issue, as it doesn't show there.
--
Matt Warnock <[email protected]>
RidgeCrest Herbals, Inc.
On Tue, 2010-08-31 at 14:45 +0200, Jacques Le Roux wrote:
From: "Carsten Schinzer" <[email protected]>
> Incredible how the original topic now turned into something pretty different
> ... it's just great!
Yes :D Actually Matt 1st hacked Jonatan's thread Error generating PDF invoice
http://markmail.org/message/vmon3ig3smles7k3
Jacques
> Matt, if you are still following this, I have a recommendation to make for
> your original point 3.
> You should start versioning your own releases (I do the same) and integrate
> a later revision of OFBiz every now and then.
>
> The trick is know as Subversion "Vendor Branch" and it is described in
> detail here:
> http://svnbook.red-bean.com/en/1.5/svn.advanced.vendorbr.html
There are also alternatives suggested in wiki
https://cwiki.apache.org/confluence/display/OFBIZ/Online+Developers+Section
Jacques
> Try it out and you will see: after some 2-3 updates from the vendor's
> repository (in this case OFBiz'), you will feel safe with the procedure. And
> you should then also be able to automate it using scripting.
>
> I still recommend you use an official release branch of OFBiz rather than
> trunk, but using this recommendation will actually allow you to do
> "fallbacks" on arbitrary versions of OFBiz trunk as long as you are
> consequently tagging your own releases.
> I do also recommend a testing stage before committing to your local
> repository and rolling on to production.
> Pros and cons on these latter two points have been addressed in the trail
> already.
>
> Hope this helps!
>
> Regards
>
>
> Carsten
>
