Hi,
> MEMOEDIT() users pls make tests.
Looks OK from dbu.
Jerry
--
___
Surf the Web in a faster, safer and easier way:
Download Opera 9 at http://www.opera.com
Powered by Outblaze
___
Harbour mailing
On 2010 Jan 22, at 12:39, Alex Strickland wrote:
> francesco perillo wrote:
>
>> Please report them in a way that can be easily understood which commit
>> they belong to.
>
> I hope this is suitable, I only included fixes to core features.
>
> 2010-01-21 16:59 UTC+0100 Viktor Szakats (harbour.
francesco perillo wrote:
Please report them in a way that can be easily understood which commit
they belong to.
I hope this is suitable, I only included fixes to core features.
2010-01-21 16:59 UTC+0100 Viktor Szakats (harbour.01 syenar.hu)
* src/rtl/memoedit.prg
! Fixed to not return e
Hi,
> 1)
> Please try to isolate commits with [TOMERGE 2.0] so we don't have, in
> a single commit, hunks that must be ported and hunks that shouldn't...
I'll try... but sometimes I just stick [TOMERGE 2.0] later,
because I forget about it or I'm unsure about back-porting
at commit time (= befo
On Fri, Jan 22, 2010 at 10:06 AM, Alex Strickland wrote:
> francesco perillo wrote:
>
>> I'm preparing to do merging in 2.0
>
> That is good of you.
>
> I noticed that there were a few bug fixes that did not appear to be marked
> with TOMERGE, did you notice them?
No, I didn't.
Up to now I export
I'm preparing to do merging in 2.0
1)
Please try to isolate commits with [TOMERGE 2.0] so we don't have, in
a single commit, hunks that must be ported and hunks that shouldn't...
I cherry-picked the commits (about 32 up to now) that should be ported
and now I will try to expunge all the hunks tha
francesco perillo wrote:
I'm preparing to do merging in 2.0
That is good of you.
I noticed that there were a few bug fixes that did not appear to be marked with
TOMERGE, did you notice them?
If not I will try and have a look through the ChangeLog and report them. As
ever, I am behind the
