I'm happy too
Phil--
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/___
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.so
On 2014-08-20 11:29-0400 Hazen Babcock wrote:
> On 8/20/2014 5:51 AM, plplot-devel-requ...@lists.sourceforge.net wrote:
>> Date: Tue, 19 Aug 2014 12:24:54 -0700 (PDT)
>> From: "Alan W. Irwin"
>
> ..
>
>> In sum, I think rebase-only is not only back on the table for our
>> initial workflow model d
On 2014-08-20 09:07-0700 phil rosenberg wrote:
> Hi Alan
> Re rebase, and shared topic branches see the second half
of http://git-scm.com/book/en/Git-Branching-Rebasing. I still don't
fully understand the implications, but it seems that if you branch
from a branch that gets rebased, then you can/
I've just been having a look through the plexit calls. 99% of them are to do
with memory allocation. I've begun creatin a plxxxarray structure where xxx
could be flt, int, char, color etc to try to make memory management easier. The
struct will contain the memory itself, the size of the array an
Hi Alan
Re rebase, and shared topic branches see the second half of
http://git-scm.com/book/en/Git-Branching-Rebasing. I still don't fully
understand the implications, but it seems that if you branch from a branch that
gets rebased, then you can/will end up with the same changes being included
Correcting the subject line..
On 8/20/2014 11:29 AM, Hazen Babcock wrote:
> On 8/20/2014 5:51 AM, plplot-devel-requ...@lists.sourceforge.net wrote:
>> Date: Tue, 19 Aug 2014 12:24:54 -0700 (PDT)
>> From: "Alan W. Irwin"
>
> ..
>
>> In sum, I think rebase-only is not only back on the table for ou
On 8/20/2014 5:51 AM, plplot-devel-requ...@lists.sourceforge.net wrote:
> Date: Tue, 19 Aug 2014 12:24:54 -0700 (PDT)
> From: "Alan W. Irwin"
..
> In sum, I think rebase-only is not only back on the table for our
> initial workflow model due to Brad's recommendation of it for that
> purpose but
On 2014-08-20 10:50+0100 Phil Rosenberg wrote:
> Hi Alan
> Just so you know, I have no real preference for either a merge or a rebase
> workflow.
> I feel that merge is more idealistically "gittish" but pragmatically
the rebase workflow might be easier. The downside is that branches
which have b
Hi Alan
Just so you know, I have no real preference for either a merge or a rebase
workflow.
I feel that merge is more idealistically "gittish" but pragmatically the rebase
workflow might be easier. The downside is that branches which have been shared
should not be rebased, because work that br
