On Fri, Apr 15, 2011 at 9:27 AM, Jouni K. Seppänen wrote:
> Benjamin Root writes:
>
> > Would a change to the v1.0.x branch "stay" on the v1.0.x branch, or is
> > there something I have to do to prevent subsequent merges from going
> > into master?
>
> Since v1.0.x is supposed to be merged into
Benjamin Root writes:
> Would a change to the v1.0.x branch "stay" on the v1.0.x branch, or is
> there something I have to do to prevent subsequent merges from going
> into master?
Since v1.0.x is supposed to be merged into master frequently, your
change would propagate into master. To prevent i
On Thu, Apr 14, 2011 at 5:54 PM, John Hunter wrote:
>
>
>
>
> On Apr 14, 2011, at 5:08 PM, Benjamin Root wrote:
>
> It was added a while back, unless I only added it to the master...?
>
>
> Could be. It appears the mplot3d tutorial rest document in the release
> branch refers to it, but it is no
On Apr 14, 2011, at 5:08 PM, Benjamin Root wrote:
> It was added a while back, unless I only added it to the master...?
>
Could be. It appears the mplot3d tutorial rest document in the release branch
refers to it, but it is not committed in the branch. You can either commit the
file or re
It was added a while back, unless I only added it to the master...?
Ben Root
On Thu, Apr 14, 2011 at 4:39 PM, John Hunter wrote:
> Doc build is failing with a missing file
>
> .. plot:: mpl_examples/mplot3d/contourf3d_demo2.py
>
> I can work around it, but this should get added...
>
> JDH
>
---
Doc build is failing with a missing file
.. plot:: mpl_examples/mplot3d/contourf3d_demo2.py
I can work around it, but this should get added...
JDH
--
Benefiting from Server Virtualization: Beyond Initial Workload
Conso
