On 2/28/09, Per Inge Mathisen <[email protected]> wrote: > Hello, > > I have been doing some backporting for Buginator today, because he has > such trouble getting into gna.org (a subject worth a discussion of its > own), but I have noticed that he is not the only one who is forgetting > to backport changes. We now have a 2.2 branch that pretty much > everyone agreed was a good idea, and it is already diverging rapidly > from trunk. Even though backporting can be a boring hassle, let me > assure you that it is *much* easier to do it sooner rather than later. > So please everyone, backport your relevant bugfixes as soon as > possible. > > Gerard, I am looking at you in particular. > > - Per
For what it is worth, as soon as the connection issues are worked out with GNA, I do plan to backport, using the same script that Giel is using. http://subversion.tigris.org/tools_contrib.html#svnmerge_py http://subversion.tigris.org/tools_contrib.html#svnmerge_sh (Which is also built in to TortoiseSVN now, but without a reliable connection, I get the old 'Connection closed unexpectedly' errors, so it won't allow the merge to continue.) I hate to spam the list with the same question again, but is there any *good* reason why we still support 2.1, and not just go directly to a 2.2 release instead? Has anyone notice anything that is a show stopper for 2.2? _______________________________________________ Warzone-dev mailing list [email protected] https://mail.gna.org/listinfo/warzone-dev
