backporting typo fixes?

Hi everyone,

I just committed a big typos fix to trunk (r8925), should changes
like this be backported to the maintenance branch?

best,

···

--
Paul Ivanov
314 address only used for lists, off-list direct email at:
http://pirsquared.org | GPG/PGP key id: 0x0F3E28F7

Big thank you for correcting those typos where virtually all of them are mine.

I'm +1 for backporting these changes as they will not break anything.
But others may have different ideas.

Regards,

-JJ

···

On Tue, Jan 18, 2011 at 4:35 AM, Paul Ivanov <pivanov314@...149...> wrote:

Hi everyone,

I just committed a big typos fix to trunk (r8925), should changes
like this be backported to the maintenance branch?

best,
--
Paul Ivanov
314 address only used for lists, off-list direct email at:
http://pirsquared.org | GPG/PGP key id: 0x0F3E28F7

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEARECAAYFAk00mfQACgkQe+cmRQ8+KPe3GgCeJfWOFkR3eVcxFmk6LoBLfwBX
QfoAn00POewPxxsyz+x3pMV2QKlcxRuh
=cNxK
-----END PGP SIGNATURE-----

------------------------------------------------------------------------------
Protect Your Site and Customers from Malware Attacks
Learn about various malware tactics and how to avoid them. Understand
malware threats, the impact they can have on your business, and how you
can protect your company and customers by using code signing.
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

Big thank you for correcting those typos where virtually all of them are mine.

I'm +1 for backporting these changes as they will not break anything.
But others may have different ideas.

I'm roughly neutral; I would only caution that when backporting, one needs to tell svnmerge about it. Something like:

svnmerge merge -S v1 -r NUM --record-only
svn commit -F svnmerge-commit-message.txt

where you are in your trunk checkout, and NUM is the revision in which you did the backporting.

Eric

···

On 01/19/2011 07:25 PM, Jae-Joon Lee wrote:

Regards,

-JJ

On Tue, Jan 18, 2011 at 4:35 AM, Paul Ivanov<pivanov314@...149...> wrote:

Hi everyone,

I just committed a big typos fix to trunk (r8925), should changes
like this be backported to the maintenance branch?

best,
--
Paul Ivanov

My vote is to backport those fixes. This way, distro maintainers can release a patch for the docs if they wish, and anyone else checking out the maintenance releases would get those fixes for their docs. I personally have a few fellow students who I set them up with matplotlib built from the maintenance branch.

Also, if – and this is a big if – we decide to release another bugfix release, the docs will be ready to go.

Ben Root

P.S. - Good to know that is how to do a backport using svnmerge. Maybe we should add that to the coding guide? (Obviously, we would want major notes pointing out that the preferred procedure is to commit to the maintenance branch and then svnmerge to the maintenance branch.)

···

On Thu, Jan 20, 2011 at 1:25 AM, Eric Firing <efiring@…229…> wrote:

On 01/19/2011 07:25 PM, Jae-Joon Lee wrote:

Big thank you for correcting those typos where virtually all of them are mine.

I’m +1 for backporting these changes as they will not break anything.

But others may have different ideas.

I’m roughly neutral; I would only caution that when backporting, one

needs to tell svnmerge about it. Something like:

svnmerge merge -S v1 -r NUM --record-only

svn commit -F svnmerge-commit-message.txt

where you are in your trunk checkout, and NUM is the revision in which

you did the backporting.

Eric