| Lists: | pgsql-hackers |
|---|
| From: | Peter Mount <petermount(at)it(dot)maidstone(dot)gov(dot)uk> |
|---|---|
| To: | "'Ansley, Michael'" <Michael(dot)Ansley(at)intec(dot)co(dot)za>, "'pgsql-hackers(at)postgresql(dot)org'" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | RE: [HACKERS] CVS |
| Date: | 1999-07-19 09:09:59 |
| Message-ID: | 1B3D5E532D18D311861A00600865478CA0CD@exchange1.nt.maidstone.gov.uk |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Lists: | pgsql-hackers |
Good question. I was going to do a fresh checkout tomorrow, but it would
be interesting to know about this.
Peter
--
Peter Mount
Enterprise Support
Maidstone Borough Council
Any views stated are my own, and not those of Maidstone Borough Council.
-----Original Message-----
From: Ansley, Michael [mailto:Michael(dot)Ansley(at)intec(dot)co(dot)za]
Sent: 19 July 1999 09:41
To: 'pgsql-hackers(at)postgresql(dot)org'
Subject: [HACKERS] CVS
Once a new tag or release has been applied to the CVS tree, is a new
checkout required, or can I just update with the new tag? Do I need to
specify a tag when updating? If not, which branch is used? Are there
separate branches for 6.5 bug-fixes and 6.6 development?
MikeA
| From: | The Hermit Hacker <scrappy(at)hub(dot)org> |
|---|---|
| To: | Peter Mount <petermount(at)it(dot)maidstone(dot)gov(dot)uk> |
| Cc: | "'Ansley, Michael'" <Michael(dot)Ansley(at)intec(dot)co(dot)za>, "'pgsql-hackers(at)postgresql(dot)org'" <pgsql-hackers(at)postgreSQL(dot)org> |
| Subject: | RE: [HACKERS] CVS |
| Date: | 1999-07-19 14:03:18 |
| Message-ID: | Pine.BSF.4.05.9907191102410.64002-100000@thelab.hub.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Lists: | pgsql-hackers |
On Mon, 19 Jul 1999, Peter Mount wrote:
> Good question. I was going to do a fresh checkout tomorrow, but it would
> be interesting to know about this.
If you do a fresh checkout, it will take the 'current' or 'ongoing' trunk
of the tree...if you want to work on a branch, you have to stipulate the
-r option to check that one out seperately...
>
> Peter
>
> --
> Peter Mount
> Enterprise Support
> Maidstone Borough Council
> Any views stated are my own, and not those of Maidstone Borough Council.
>
>
>
> -----Original Message-----
> From: Ansley, Michael [mailto:Michael(dot)Ansley(at)intec(dot)co(dot)za]
> Sent: 19 July 1999 09:41
> To: 'pgsql-hackers(at)postgresql(dot)org'
> Subject: [HACKERS] CVS
>
>
> Once a new tag or release has been applied to the CVS tree, is a new
> checkout required, or can I just update with the new tag? Do I need to
> specify a tag when updating? If not, which branch is used? Are there
> separate branches for 6.5 bug-fixes and 6.6 development?
>
> MikeA
>
>
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: scrappy(at)hub(dot)org secondary: scrappy(at){freebsd|postgresql}.org
| From: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Peter Mount <petermount(at)it(dot)maidstone(dot)gov(dot)uk> |
| Cc: | "'Ansley, Michael'" <Michael(dot)Ansley(at)intec(dot)co(dot)za>, "'pgsql-hackers(at)postgresql(dot)org'" <pgsql-hackers(at)postgreSQL(dot)org> |
| Subject: | Re: [HACKERS] CVS |
| Date: | 1999-07-19 14:29:12 |
| Message-ID: | 199907191429.KAA08472@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Lists: | pgsql-hackers |
> Good question. I was going to do a fresh checkout tomorrow, but it would
> be interesting to know about this.
>
>
> Once a new tag or release has been applied to the CVS tree, is a new
> checkout required, or can I just update with the new tag? Do I need to
> specify a tag when updating? If not, which branch is used? Are there
> separate branches for 6.5 bug-fixes and 6.6 development?
>
Current 6.6 is cvs without tags. 6.5.1 is tag REL6_5_PATCHES.
--
Bruce Momjian | http://www.op.net/~candle
maillist(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026