pg.ddx.io  pgsql-interfaces@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bruce Momjian <pgman@candle.pha.pa.us>
To: D'Arcy J.M. Cain <darcy@druid.net>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Gaetano Mendola <mendola@bigfoot.com>
Cc: PostgreSQL-interfaces <pgsql-interfaces@postgresql.org>
Subject: Re: [ADMIN] pgdb.py is still wrong in Postgres 7.3.1 rpm
Date: Wed, 8 Jan 2003 09:48:16 -0500 (EST)
Message-ID: <200301081448.h08EmGi13991@candle.pha.pa.us> (raw)
In-Reply-To: <200301080850.06495.darcy@druid.net>

D'Arcy J.M. Cain wrote:
> On Tuesday 07 January 2003 23:12, Tom Lane wrote:
> > "D'Arcy J.M. Cain" <darcy@druid.net> writes:
> > > I'm not sure what is being asked for here.
> >
> > We'd like to put the typlen fix into the REL7_3_STABLE CVS branch.
> > Also any other post-7.3 fixes that you consider appropriate for 7.3.2
> > (ie, important, low-risk fixes).
> 
> I also just fixed that file again.  As someone else just pointed out, we need 
> to return None instead of -1 there.
> 
> > If you're not comfortable enough with CVS-munging to want to touch
> > branches other than HEAD, Bruce or I can handle it for you.  Just let
> > us know exactly which changes should be back-patched.
> 
> Sure.  Just that one and the one I just made I think.  Other things were 
> mainly feature additions.  If you can tell me what the process is or point me 
> to the relevant docs I can do this myself in the future.  I want to walk 
> softly here because I know that different projects have different rules and 
> methods for these sorts of things.

What I normally do is to do a separate checkout for the branch I want to
patch.  In this case, a cvs log on /HISTORY shows it as:

	        REL7_3_STABLE: 1.182.0.2

You know it is a branch rather than a tag because it has four numbers.
(The developers FAQ has stuff on this.)  I then make changes to that
CVS, and do a commit while sitting in that CVS tree.  I applies the
changes against that branch only.

I usually get a cvs diff from the HEAD tree, and apply that patch file
against the branch.  Let me know if you would like me to do it.

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073



view thread (8+ messages)

Message-ID: <200301081448.h08EmGi13991@candle.pha.pa.us>
Permalink:  ../200301081448.h08EmGi13991@candle.pha.pa.us/
Also on:    postgresql.org/message-id/200301081448.h08EmGi13991@candle.pha.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-interfaces@postgresql.org
  Cc: pgman@candle.pha.pa.us, darcy@druid.net, tgl@sss.pgh.pa.us, mendola@bigfoot.com
  Subject: Re: [ADMIN] pgdb.py is still wrong in Postgres 7.3.1 rpm
  In-Reply-To: <200301081448.h08EmGi13991@candle.pha.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox