Hey Ron, Thanks for the tip, I was planning to do that, but I need emails of all svn commiters.. It looks fine as it is now, ie:
changeset: 300:42414d766c45 branch: release26-maint tag: python-2.64 user: richard.tew date: Tue Oct 27 19:22:29 2009 +0000 summary: Merged r75183-75706 from standard Python release26-maint branch (Python 2.6.4 tagged revision). User is richard.tew - of course, full name with email is way better, but I'll need Richard or someone with admin SVN access to give me the list.. Thanks again, alex. On Fri, Sep 9, 2011 at 1:58 PM, Ron DuPlain <[email protected]> wrote: > Hi Alex, > > On Fri, Sep 9, 2011 at 8:39 AM, Aleksandar Radulovic <[email protected]> wrote: >> The conversion took a loong time on my virtual server at Rackspace, >> but went smoothly. The authors seem to be mapped to svn usernames >> (maybe we want to run conversion again with all the emails of people >> commiting).. > > Just making sure you save yourself the compute & network time... > > Hg's convert provides an authors mode where you can convert a > repository on local disk, changing all of the author names without > re-running the full conversion (like git filter-branch). You already > have the builtin convert extension enabled. Create an author convert > list: > > <oldname>=<newname> > > ... then run: > > hg convert --authors path/to/author.list ~/src/stack ~/src/stack-authors > > Entirely local. > > -Ron > > >> Here are the tags: >> alex@lenny:~/src/stack$ hg tags >> tip 545:a22e28ac234a >> python-2.55 534:805995910e49 >> python-2.54 527:9d1921ae3920 >> python-2.53 526:56055ccaf9d5 >> python-2.52 497:a8d523a41749 >> python-2.52c1 496:480af5a9dcc8 >> python-2.51 463:a1c739578d45 >> python-2.5 442:36fb676dca4e >> python-2.5c1 434:b38837703690 >> python-2.71 417:4332380419e0 >> python-2.65 322:4fb0ff9f6d96 >> python-2.64 300:42414d766c45 >> python-2.63 298:20ed90cfc850 >> python-2.6.2 292:0da68795ac90 >> python-2.6.1 286:a176f8c12e6a >> python-2.6 279:507e869f66d6 >> python-2.5b3 222:eadda9cd8566 >> python-2.5b2 220:0dc0f28cdd01 >> python-3.01 192:ae315c2d29e0 >> python-3.0.1 191:6ded28594d37 >> python-3.0 184:71db2c395801 >> python-3.1.3 175:bf4be7b17d59 >> python-3.12 169:99dd7f6bfbd8 >> python-3.11 157:9c05ac5b5d40 >> python-3.2 153:9985fffba844 >> python-3.1 119:061375212a12 >> python-2.44 37:22691b22d6c2 >> python-2.43 36:c61e3c87f9bd >> >> And the branches: >> alex@lenny:~/src/stack$ hg branches >> default 545:a22e28ac234a >> release25-maint 544:e103621bbf41 >> release27-maint 433:b9df342fad42 >> release26-maint 341:b7ba1737527e >> release30-maint 202:12168fe513cf >> release31-maint 181:f7e563c77801 >> release32-maint 155:de9c78664553 >> release24-maint 48:a0414e803d51 >> py3k 153:9985fffba844 (inactive) >> dev 35:496b84ab1096 (inactive) >> >> Not sure why dev and py3k are marked inactive. ;) >> >> I am pushing it to https://bitbucket.org/a13x/stackless right now, so >> you guys can clone it and test if everything's ok. This is going to >> take a while, I'll let you know when its done.. >> >> -alex >> >> >> >> On Thu, Sep 8, 2011 at 3:02 PM, Aleksandar Radulovic <[email protected]> wrote: >>> As far as I know, hg convert takes all the history (branches included) >>> from SVN and runs them in mercurial repo, step by step (including >>> merges), so it should replicate pretty much exactly what happened in >>> SVN. >>> >>> The conversion is still running, I will be able to give you more >>> answers when its done.. >>> >>> -alex >>> >>> On Thu, Sep 8, 2011 at 1:57 PM, Richard Tew <[email protected]> wrote: >>>> On Thu, Sep 8, 2011 at 9:19 PM, Aleksandar Radulovic <[email protected]> wrote: >>>>> Hehe, >>>>> >>>>> Me and my big mouth :) >>>> >>>> While it's open :-) >>>> >>>> Do you know anything about what the best approach would be with regard >>>> to different branches? Or would each branch need to be converted >>>> separately? What about their histories and their point of divergence >>>> from the python branches I branched them from - something SVN records? >>>> >>>> Cheers, >>>> Richard. >>>> >>>> _______________________________________________ >>>> Stackless mailing list >>>> [email protected] >>>> http://www.stackless.com/mailman/listinfo/stackless >>>> >>> >>> >>> >>> -- >>> a lex 13 x >>> http://www.a13x.info >>> >> >> >> >> -- >> a lex 13 x >> http://www.a13x.info >> >> _______________________________________________ >> Stackless mailing list >> [email protected] >> http://www.stackless.com/mailman/listinfo/stackless >> > > _______________________________________________ > Stackless mailing list > [email protected] > http://www.stackless.com/mailman/listinfo/stackless > -- a lex 13 x http://www.a13x.info _______________________________________________ Stackless mailing list [email protected] http://www.stackless.com/mailman/listinfo/stackless
