Yes, all that too ;-)
>>
>> On Wed, 25 Aug 1999, Ansley, Michael wrote:
>>
>> > The reason for the tag as to be able to return to the 6.5 release
source
>> > code. It's production code, and should be accessible at least for the
next
>> > couple of months.
>> >
>> > Was a tag created for 6.5.1? The object is to be able to check out any
>> > particular release, bugs and all, whenever we feel like it.
>>
>> Never did v6.5.1...but I have no problem with starting to do
>> this on minor
>> releases to, since...
>>
>> Could someone try out the following patch?
>>
>> ftp://ftp.postgresql.org/pub/postgresql-6.5-6.5.x.patch.gz
>>
>> It is a patch against v6.5 that will bring it up to the most stable
>> version *if* it worked right. Reading through the patch,
>> everything looks
>> good, but...
>>
>> If this actually works, we just might have a way of saving
>> ppl downloading
>> 5Meg files on minor releases, as the above is <100k :)
>>
>>
>> >
>> > MikeA
>> >
>> >
>> >
>> > >>
>> > >>
>> > >> Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> writes:
>> > >> > Just for a confirmation: I see REL6_5_PATCHES and REL6_5 Tag in
the
>> > >> > CVS respository. I thought that REL6_5_PATCHES is the Tag for the
6.5
>> > >> > statble tree and would eventually become 6.5.2. If so, what is the
>> > >> > REL6_5 Tag? Or I totally miss the point?
>> > >>
>> > >> Right, REL6_5_PATCHES is the 6.5.* branch. REL6_5 is just a tag ---
>> > >> that is, it's effectively a frozen snapshot of the 6.5 release,
>> > >> not an evolvable branch.
>> > >>
>> > >> I am not sure if Marc intends to continue this naming convention
>> > >> in future, or if it was just a mistake to create REL6_5 as a tag
>> > >> not a branch. I don't see a whole lot of use for the frozen tag
>> > >> myself...
>> > >>
>> > >> regards, tom lane
>> > >>
>> > >> ************
>> > >>
>> >
>> > ************
>> >
>>
>> Marc G. Fournier ICQ#7615664
>> IRC Nick: Scrappy
>> Systems Administrator @ hub.org
>> primary: scrappy(at)hub(dot)org secondary:
>> scrappy(at){freebsd|postgresql}.org
>>