On Thu, Apr 14, 2011 at 5:54 PM, John Hunter <jdh2...@gmail.com> wrote:
>
>
>
>
> On Apr 14, 2011, at 5:08 PM, Benjamin Root <ben.v.r...@gmail.com> 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 remove the doc reference from the branch.
>
Ok, I just double-check what happened. I added a feature to mplot3d, and
because it was a new feature, it was not added to the maintenance branch
(although, that is the only reason why it was not backported). The missing
demo requires that feature, therefore, it is the docs that are wrong in the
v1.0.x branch.
I am still in the middle of my work (although the load has lightened today),
and so I haven't been git-minded in a while. 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?
Ben Root
------------------------------------------------------------------------------
Benefiting from Server Virtualization: Beyond Initial Workload
Consolidation -- Increasing the use of server virtualization is a top
priority.Virtualization can reduce costs, simplify management, and improve
application availability and disaster protection. Learn more about boosting
the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev
_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
