Jonathan - I suggest you "follow" the "web2py" branch on http://www.bitbucket.org/yarko/web2py/ - that way, you'll get notices when I've mirrored new changes (like just now) - and you can update / evaluate if it affects your patch.
Also, create an account on Launchpad and "subscribe" to Massimo's web2py branch there: https://code.launchpad.net/~mdipierro/web2py/devel These are the same sorts of things on both trees. In general, if you are going to contribute, this is a good way to track what is going on in the main (and mirrored) trunks, as well as any branches you are interested in. I should collect this into developer guidelines somewhere - I'll think about starting that this weekend. Regards, Yarko On Wed, Nov 12, 2008 at 10:18 AM, Yarko T <[EMAIL PROTECTED]> wrote: > Thanks for this, Jonathan - > I'm glad you found the mirror easy (I think it's significantly fast also). > > I've attached an image showing how you can review (or try) Jonathan's > changes. > > Massimo - > > After you try a merge from bitbucket work, we will look for what you would > like done to make your life easier with this. > > NOTE: > I suggest a branch naming convention something like this: > > [trunk-name]-[topic]-[patch|devel] > > where "patch" for fixes, "devel" for additions / new functionality. > > for example, I would have named this patch: > > web2py-isurl-patch > or just: > web2py-isurl > > Thanks again! > > Kind regards, > Yarko > > On Wed, Nov 12, 2008 at 6:42 AM, Jonathan Benn <[EMAIL PROTECTED]>wrote: > >> >> Hi Yarko and Massimo, >> >> >> On Nov 11, 10:39 pm, "Yarko T" <[EMAIL PROTECTED]> wrote: >> > FYI - For those working w/ mercurial: >> > I've mirrored this morning's latest changes from Massimo tohttp:// >> bitbucket.org/yarko/web2py >> >> Wow, that was *very* usable!!! :-D I'm really impressed. The only >> snag I ran into was trying to use an OpenID account... then I couldn't >> upload changes through Mercurial because I couldn't authenticate. I >> tried creating a new account and it worked fine. >> >> I've uploaded my patch to: >> http://www.bitbucket.org/Demiurge11/patch/overview/ >> >> >> Instructions for how to do this yourself: >> >> 1. Create a new username with Bitbucket >> http://www.bitbucket.org/account/signup/ >> >> 2. Login to Bitbucket (if you haven't already done so) >> >> 3. Go to the web2py mirror on Bitbucket: >> http://www.bitbucket.org/yarko/web2py/ >> >> 4. Click on the "fork" button >> >> 5. Enter the name of your fork and a description and then click on >> "Create Fork" >> >> 6. You're done! The overview website tells you which Hg commands to >> use. Basically, Bitbucket just hosts a Mercurial repository for you, >> which you can access using the normal Mercurial mechanisms. It's >> really neat! This is honestly the easiest version control I've ever >> done (I've used CVS and Clearcase previously). >> >> Ok, everyone please let me know if you notice any problems with the >> patch and I'll be happy to fix them. >> >> --Jonathan >> >> >> > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to web2py@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
