Re: [matplotlib-devel] svnmerge broken?

2009-01-17 Thread Eric Firing
Michael Droettboom wrote: > You need the '-S' parameter to specify a branch. Otherwise, any > arguments after the command name are just paths within the working copy, > just like most other svn commands. > > So you need to do: > >> svnmerge.py merge -S v0_98_5_maint > > I just tested a change

Re: [matplotlib-devel] svnmerge broken?

2009-01-17 Thread Michael Droettboom
You need the '-S' parameter to specify a branch. Otherwise, any arguments after the command name are just paths within the working copy, just like most other svn commands. So you need to do: > svnmerge.py merge -S v0_98_5_maint I just tested a change to the branch followed by a merge and ever

Re: [matplotlib-devel] svnmerge broken?

2009-01-17 Thread Eric Firing
John Hunter wrote: > After reading in a separate thread that Eric was having trouble with > svnmerge, I gave it a try and got > > jdhun...@uqbar:mpl> svnmerge.py merge v0_98_5_maint > svnmerge: "v0_98_5_maint" is not a subversion working directory > > Maybe our svn merge guru (MD) could take

[matplotlib-devel] svnmerge broken?

2009-01-17 Thread John Hunter
After reading in a separate thread that Eric was having trouble with svnmerge, I gave it a try and got jdhun...@uqbar:mpl> svnmerge.py merge v0_98_5_maint svnmerge: "v0_98_5_maint" is not a subversion working directory Maybe our svn merge guru (MD) could take a look and see if anything looks

[matplotlib-devel] savefig with tight bounding box.

2009-01-17 Thread Jae-Joon Lee
Hi all, I added an (experimental) bbox_inches option for savefig in the trunk. If provided, only the specified area of the figure will be saved. bbox_inches can be "tight", and a tight bounding box is internally estimated (but this draws the figure twice). Take a look at "demo_tightbbox.py". The