Re: psycopg repository moved to bzr
"James Henstridge" <[email protected]>
| Newsgroups | gmane.comp.python.db.psycopg.devel |
|---|---|
| Message-ID | <[email protected]> |
On 26/04/2008, Tim Roberts <[email protected]> wrote: > Jerry LeVan wrote: > > On Apr 25, 2008, at 5:01 PM, Federico Di Gregorio wrote: > > > > > > >> ...while read-only access is available using HTTP: > > >> > >> http://initd.org/bazaar/psycopg > >> > >> federico > >> > > > > There does not seem to be anything at the http address above... > > > > > More precisely, there is a directory tree, but it is not populated with > any files. The Bazaar branches do not have any working tree files, yes. There are .bzr directories though, which are hidden by the Apache directory listings. If you want to play around with the source code, I'd suggest doing the following: 1. Install Bazaar. I'd recommend the latest stable version (1.3.1), but anything >= 1.0 should do. See http://bazaar-vcs.org/ for details. 2. Tell Bazaar what commit ID to use. You only need to do this once: bzr whoami "James Henstridge <[email protected]>" 3. Grab a copy of the branch: bzr branch http://initd.org/bazaar/psycopg/psycopg2/branches/2_0_x/ psycopg2 4. Make your changes. You can commit as often as you want. You have a local copy of the history, so "bzr diff", "bzr annotate", etc should be fairly fast and can be done offline. 5. Create a bundle for your changes, and attach it in the bug tracker or send to the list: bzr bundle -o my-changes.patch We can then merge your changes, and they'll be credited to you in annotate output and logs rather than the person who merged them. If you are just interested in having a local copy of the development head, steps (1) and (3) are all you need. You can then run "bzr pull" to update that tree. James.