From: | The Hermit Hacker <scrappy(at)hub(dot)org> |
---|---|
To: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | PostgreSQL-development <hackers(at)postgreSQL(dot)org> |
Subject: | Re: [HACKERS] cvs and empty directories |
Date: | 1998-07-21 00:22:38 |
Message-ID: | Pine.BSF.3.96.980720212058.13063B-100000@thelab.hub.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, 20 Jul 1998, Bruce Momjian wrote:
> I have found cvs creating many directories that I know were removed from
> the source tree. I now use the -P option to cvs update/checkout to
> prevent this from happening.
>
> -P Prune (remove) directories that are empty after
> being updated, on checkout, or update. Normally,
> an empty directory (one that is void of revision-
> controlled files) is left alone. Specifying -P
> will cause these directories to be silently removed
> from your checked-out sources. This does not
> remove the directory from the repository, only from
> your checked out copy. Note that this option is
> implied by the -r or -D options of checkout and
> export.
The general recommendation that I've received concerning this is
to run:
cvs -q update -APd
-q puts it in a quiet mode, so only changes are reported
-A removes any sticky tags to give you CURRENT sources
-P Prunes (as above)
-d creates any new directories required
Marc G. Fournier
Systems Administrator @ hub.org
primary: scrappy(at)hub(dot)org secondary: scrappy(at){freebsd|postgresql}.org
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas G. Lockhart | 1998-07-21 01:41:21 | Re: [HACKERS] Finding primary keys in a table |
Previous Message | Paul A Vixie | 1998-07-20 23:56:17 | Re: [HACKERS] cidr |