:-) I glad that's sorted out, as I don't think I've ever made any
commits to WSJT-X branches .. If I did, it was minor, and a long time ago.
You had me thinking something was seriously amiss :-)
73's
Greg, KI7MT
On 9/26/2014 01:00, Bill Somerville wrote:
> On 26/09/2014 01:57, Joe Taylor wrote:
:-) I glad that's sorted out, as I don't think I've ever made any
commits to WSJT-X branches .. If I did, it was minor, and a long time ago.
You had me thinking something was seriously amiss :-)
73's
Greg, KI7MT
On 9/26/2014 01:00, Bill Somerville wrote:
> On 26/09/2014 01:57, Joe Taylor wrote:
On 26/09/2014 01:44, Joe Taylor wrote:
> Hi Bill,
Hi Joe,
>
> Joe:
>>> All seems OK to me, except possibly for your parenthetical statement
>>> "one day we really need to move this to trunk".
>>> We can't do this unless we give up the notion that WSJT, MAP65, WSPR,
>>> WSPR-X, and WSJT-X are all pa
On 26/09/2014 01:57, Joe Taylor wrote:
> Hi Bill,
Hi Joe,
>
>> Greg (KI7MT) has checked out the WSJT-X v1.4 branch branches/wsjtx-1.4
>> and made a change that needs to go into the next release candidate
>> wsjtx-1.4.0-rc2. At the time of writing he has committed the change to
>> the branch but not
Hi Bill,
> Greg (KI7MT) has checked out the WSJT-X v1.4 branch branches/wsjtx-1.4
> and made a change that needs to go into the next release candidate
> wsjtx-1.4.0-rc2. At the time of writing he has committed the change to
> the branch but not yet merged it into the main line (branches/wsjtx).
A
Hi All,
branching and merging in source control is often a source of confusion
and seems daunting at first so here is an example that covers the
"Release branch" situation we are currently in.
Greg (KI7MT) has checked out the WSJT-X v1.4 branch branches/wsjtx-1.4
and made a change that needs t
Hi Bill,
Joe:
>> All seems OK to me, except possibly for your parenthetical statement
>> "one day we really need to move this to trunk".
>> We can't do this unless we give up the notion that WSJT, MAP65, WSPR,
>> WSPR-X, and WSJT-X are all part of the same "project". Historically,
>> the "trunk:
On 26/09/2014 00:03, KI7MT wrote:
> Hi Joe, Bill,
Hi Greg,
>
> I just want to make sure I understand all this now. If we use the
> standard branch head for WSJTX, that is now being called wsjtx v1.5?
Yes, actually wsjtx-1.5.0-rc1.
>
> And to pull WSJTX-1.4.0-RC1, we use:
>
> svn co https://svn.code
Hi Joe, Bill,
I just want to make sure I understand all this now. If we use the
standard branch head for WSJTX, that is now being called wsjtx v1.5?
And to pull WSJTX-1.4.0-RC1, we use:
svn co https://svn.code.sf.net/p/wsjt/wsjt/tags/wsjtx-1.4.0-rc1
or
svn co https://svn.code.sf.net/p/wsjt/wsj
On 25/09/2014 21:57, Joe Taylor wrote:
> Hi Bill,
Hi Joe,
>
> Thanks for posting a clear statement of correct repository procedures
> going forward.
>
> All seems OK to me, except possibly for your parenthetical statement
> "one day we really need to move this to trunk".
> We can't do this unless w
Hi Bill,
Thanks for posting a clear statement of correct repository procedures
going forward.
All seems OK to me, except possibly for your parenthetical statement
"one day we really need to move this to trunk".
We can't do this unless we give up the notion that WSJT, MAP65, WSPR,
WSPR-X, and W
Hi Billyep im on Linux...ok will try and follow your instructions
for the update of Hamlib3
Just worked Pierre F5LMI with about 30 watts so the new update of WSJT-X
is working well
73 David VK4BDJ
On 26/09/14 06:25, Bill Somerville wrote:
> On 25/09/2014 21:02, David wrote:
> Hi David,
On 25/09/2014 21:02, David wrote:
Hi David,
> Hi Joe and all.i have just done an update of WSJT-X using a script i
> put together from the origional lines for cmake sent out by Bill
> im now showing WSJT-X v1.5.0-c1 r4375
> looks goodwill check it all out and report any problems
>
> Bill...
Hi Joe and all.i have just done an update of WSJT-X using a script i
put together from the origional lines for cmake sent out by Bill
im now showing WSJT-X v1.5.0-c1 r4375
looks goodwill check it all out and report any problems
Bill...im still using your origonal hamlib 3 files you sent
Mike --
> Credits mismatch between About window and the manual
Thanks for catching this discrepancy. The online manual has been fixed;
we'll need to correct the list in "About" in rc2.
-- Joe, K1JT
--
Meet PCI
Hi All,
the first cut of v1.4.0 has been made. The tag tags/wsjtx-1.4.0-rc1 has
been recorded.
Anyone making a distribution kit for the upcoming Beta release of v1.4.0
must checkout this tag and ensure you have a clean source tree before
building it. Do not commit any changes to the tag as it
Credits mismatch between About window and the manual
About has W9MDB
Manual has KI7MT
So they're not quite in sync.
Mike W9MDB
--
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve P
On 25/09/2014 19:39, Josh Rovero wrote:
Hi Josh,
Bill Somerville mailto:g4...@classdesign.com>>
asked:
> That is indeed a defect, but why are you not using the CMake build?
I'm pretty comfortable with qmake and build/run several other Qt
projects that way. WSJTX is the only cmake project, Cma
Bill Somerville asked:
> That is indeed a defect, but why are you not using the CMake build?
I'm pretty comfortable with qmake and build/run several other Qt
projects that way. WSJTX is the only cmake project, Cmake builds
it, but doesn't install it the way I expect it to. Yeah, old dog, new
t
Ensure you have the following file and contents
qmake_only/svnversion.h
Should contain
/* This is a dummy file required to make the qmake build compatible
with the CMake build. */
#define WSJTX_STRINGIZE(X)
Mike W9MDB
From: Josh Rovero [mailto:josh.rov...@gmail.com]
Sent:
On 25/09/2014 18:50, Josh Rovero wrote:
Hi Josh,
Getting following error with revision_utils.cpp, looks like missing
right brace
wsjtx_src/revision_utils.cpp
../wsjtx_src/revision_utils.cpp: In function 'QString
program_title(const QString&)':
../wsjtx_src/revision_utils.cpp:85:30: error: e
Getting following error with revision_utils.cpp, looks like missing right
brace
wsjtx_src/revision_utils.cpp
../wsjtx_src/revision_utils.cpp: In function 'QString program_title(const
QString&)':
../wsjtx_src/revision_utils.cpp:85:30: error: expected '}' before ';' token
QString id {"WSJT-X v1.4
Hi Bill,
On 9/25/2014 17:20, Bill Somerville wrote:
> On 25/09/2014 18:14, KI7MT wrote:
>> HI Bill,
> Hi Greg,
>>
>> On 9/25/2014 17:07, Bill Somerville wrote:
>>> On 25/09/2014 17:50, KI7MT wrote:
Hi Bill,
>>> Hi Greg,
On 9/25/2014 16:28, Bill Somerville wrote:
> On 25/09/2014 15:39
On 25/09/2014 18:14, KI7MT wrote:
> HI Bill,
Hi Greg,
>
> On 9/25/2014 17:07, Bill Somerville wrote:
>> On 25/09/2014 17:50, KI7MT wrote:
>>> Hi Bill,
>> Hi Greg,
>>> On 9/25/2014 16:28, Bill Somerville wrote:
On 25/09/2014 15:39, Joe Taylor wrote:
Hi Joe,
> RR Bill, thanks for the up
Hi all,
> OK, I think I'm done.
Full marks, indeed -- to all who have contributed so much! Bill, would
you like to create a tag of .../branches/wsjtx at r4370? Packages for
WSJT-X-1.4.0-rc1 would then be built from that revision, for all
supported platforms.
-- Joe
HI Bill,
On 9/25/2014 17:07, Bill Somerville wrote:
> On 25/09/2014 17:50, KI7MT wrote:
>> Hi Bill,
> Hi Greg,
>>
>> On 9/25/2014 16:28, Bill Somerville wrote:
>>> On 25/09/2014 15:39, Joe Taylor wrote:
>>> Hi Joe,
RR Bill, thanks for the update.
>>> OK, I think I'm done.
>>>
>>> The Linux pa
On 25/09/2014 17:50, KI7MT wrote:
> Hi Bill,
Hi Greg,
>
> On 9/25/2014 16:28, Bill Somerville wrote:
>> On 25/09/2014 15:39, Joe Taylor wrote:
>> Hi Joe,
>>> RR Bill, thanks for the update.
>> OK, I think I'm done.
>>
>> The Linux package building is still short of making compliant packages
>> but
Hi Bill,
> OK, I think I'm done
Full marks, Bill, for all your hard work...is r4370 the magic number?
(Currently running on 10.9.4)
--- John G4KLA
--
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achi
Hi Bill,
On 9/25/2014 16:28, Bill Somerville wrote:
> On 25/09/2014 15:39, Joe Taylor wrote:
> Hi Joe,
>> RR Bill, thanks for the update.
> OK, I think I'm done.
>
> The Linux package building is still short of making compliant packages
> but at least some sort of package (DEB and RPM) can be ge
On 25/09/2014 15:39, Joe Taylor wrote:
Hi Joe,
> RR Bill, thanks for the update.
OK, I think I'm done.
The Linux package building is still short of making compliant packages
but at least some sort of package (DEB and RPM) can be generated which
will at least install and run from in system direct
RR Bill, thanks for the update.
-- Joe
On 9/25/2014 10:18 AM, Bill Somerville wrote:
> On 25/09/2014 15:13, Joe Taylor wrote:
>> Hi all,
> Hi Joe,
>>
>> Does anyone have last-minute "must do" commits for the WSJT-X code?
>> Are we converging toward tagging revision 4363 as "release candid
On 25/09/2014 15:13, Joe Taylor wrote:
> Hi all,
Hi Joe,
>
> Does anyone have last-minute "must do" commits for the WSJT-X code?
> Are we converging toward tagging revision 4363 as "release candidate 1"
> for version 1.4.0 ?
I am still working through the consequences of adding in the local user
g
Hi all,
Does anyone have last-minute "must do" commits for the WSJT-X code?
Are we converging toward tagging revision 4363 as "release candidate 1"
for version 1.4.0 ?
-- Joe, K1JT
--
Meet PCI DSS 3.0 Compliance
On 25/09/2014 03:57, Laurie VK3AMA wrote:
Hi Bill,
Hi again Laurie,
Contrary to my last post, the Alt numeric number Hotkey alternative
works but leaves a garbage character in whatever edit field contained
the insertion point prior to issuing the HotKey.
I have hacked a workaround so don't
On 25/09/2014 03:57, Laurie VK3AMA wrote:
Hi Bill,
Hi Laurie,
Contrary to my last post, the Alt numeric number Hotkey alternative
works but leaves a garbage character in whatever edit field contained
the insertion point prior to issuing the HotKey.
Yes, that's the mechanism for entering non-
35 matches
Mail list logo
