I can branch at 4840 or 4841 and leave your patch in, but we need to
figure out which is the branch point fairly quickly before someone tries
to create a bug fix for the stable code. I'll also need to bump the
revision in trunk to avoid confusion.
On 2/3/12 12:12 AM, Brian Hinz wrote:
> Sorry, m
Sorry, my bad, I thought you had actually branched 1.2 already. I don't
think this is release ready code, would it make more sense to branch at
4840 or 4841, or for me to back out 4842 temporarily and re-apply after you
branch?
Thanks,
-brian
On Fri, Feb 3, 2012 at 12:51 AM, DRC wrote:
> I hadn
I hadn't actually branched 1.2 yet, so trunk is still supposed to be
stable. I was waiting for a more reasonable explanation of 4841 from
Pierre before branching, as that patch appears destabilizing as well.
On 2/2/12 11:38 PM, bph...@users.sourceforge.net wrote:
> Revision: 4842
> htt
Feature Request Tracker item #3482254, was opened at 2012-01-31 08:47
Message generated for change (Comment added) made by dcommander
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=1126849&aid=3482254&group_id=254363
Please note that this message will contain a ful
Feature Request Tracker item #3482254, was opened at 2012-01-31 08:47
Message generated for change (Comment added) made by bphinz
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=1126849&aid=3482254&group_id=254363
Please note that this message will contain a full co
Feature Request Tracker item #3482254, was opened at 2012-01-31 08:47
Message generated for change (Comment added) made by afluegel
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=1126849&aid=3482254&group_id=254363
Please note that this message will contain a full
