Update included popt to version 1.7

[jw schultz]

On Sat, May 03, 2003 at 11:50:37PM -0700, Jos Backus wrote:
> On Sun, May 04, 2003 at 01:41:53AM +0100, Max Bowsher wrote:
> > Don't do that - you use the same vendor branch to hold multiple imported
> > versions, so forcing it to 1.7.1 is just misleading. Better to let it
> > default to 1.1.1, so people immediately notice it is a vendor branch. (Yes,
> > I know 1.7.1 can only be a vendor branch since it ends in an odd number, but
> > it's not what most people are accustomed to seeing.)
> 
> I must be the only one who finds this a very arcane way of doing things.
> Fwiw, here's a description of how to do this with Perforce, which I at least
> find easier. Ymmv.
> 
>     http://www.catnook.com/doc/p4-vendor-branching.html

In this context I don't care how perfoce does it.  I am not
going to bury the discussion of changing SCM systems in a
popt update thread.  Please stay on-topic.

If you want to do a vendor branch in CVS for the popt
resync, OK.  If you don't, that's OK too, but consider
making a symbolic tag to help the process next time.

-- 
________________________________________________________________
	J.W. Schultz            Pegasystems Technologies
	email address:		jw at pegasys.ws

		Remember Cernan and Schmitt