Re: [ADMIN] pgdb.py is still wrong in Postgres 7.3.1 rpm

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,
Pennsylvania19073