In addition to Alan's suggestion, another approach would be to setup a local
bare git repo that all your local machines could push/pull to/from.
I tried this. As soon as I rebase a branch I am no longer able to push
it to the local bare repo because all the changes made since the last
push no
Hi Alan
Great detective work!!!
In response to your question, why do we need a random name? If there
is already an instance of wxPLViewer running or if there is another
example running and we try to create another instance we will try to
generate another region of shared memory with the same
why does plplotMemoryMapAA and
plplotMemoryMapVDXVDZXFQI always appear to succeed and
plplotMemoryMapQQ always appear to fail?
Forgot to answer this - my response though is that I have no idea!
--
On 2015-02-22 12:52- Phil Rosenberg wrote:
The git format-patch and git am method has recently worked well to
share experimental development work from one of your computers to
mine.
This has the same downsides. As soon as I rebase a branch all patched
repos which included the rebased
Hi, Phil.
On Feb 22, 2015, at 4:52 AM, Phil Rosenberg wrote:
In addition to Alan's suggestion, another approach would be to setup a
local bare git repo that all your local machines could push/pull to/from.
I tried this. As soon as I rebase a branch I am no longer able to push
it to the
Hi Alan
Thanks for the thoughts. I will try your option II, but I suspect that the two
rebases will give different guide to the reapplied commits so I will not be
able to do a --ff-only merge between the two. I suspect the same might occur
for your option III, however that process is getting so
@Jim: could you please try the attached patch on Mac OS X, and
especially the test mentioned in the commit message?
@Phil: could you do the same thing on CentOS and Ubuntu?
More below in context.
On 2015-02-22 10:39- Phil Rosenberg wrote:
Hi Alan
Great detective work!!!
In response to
To all PLplot developers:
In my role as PLplot release manager, I am now declaring a soft freeze
for pushes to origin master which will continue until the release is
completed next Saturday (Febrary 28th). So please continue your
development on your own personal PLplot topic branches, but only
Yep, will do. I was just setting up to do that today.
On Feb 22, 2015, at 4:37 PM, Alan W. Irwin ir...@beluga.phys.uvic.ca wrote:
@Jim: could you please try the attached patch on Mac OS X, and
especially the test mentioned in the commit message?
@Phil: could you do the same thing on
On 2015-02-22 22:04-0500 Jim Dishaw wrote:
I just cloned from SF and tried to apply the patch with no success
(see below [where the git apply command was used rather than the
correct git am]).
Hi Jim:
I prepared this (one-patch) patch series with git format-patch. I am
pretty sure you should
I just cloned from SF and tried to apply the patch with no success (see below).
I can say, however, that I was able to successfully build and run ctest on
MacOS X. When I run test-plplot.sh and test_diff.sh, I get a message about
missing stdout for all the examples.
bash-3.2$ git apply
11 matches
Mail list logo
