From:	Martin Str|mberg <ams AT ludd DOT luth DOT se>
Message-Id:	<200106091729.TAA04775@mother.ludd.luth.se>
Subject:	Re: .files on servers are perceived as readonly
To:	eliz AT is DOT elta DOT co DOT il
Date:	Sat, 9 Jun 2001 19:29:32 +0200 (MEST)
Cc:	djgpp-workers AT delorie DOT com (DJGPP-WORKERS)
In-Reply-To:	<3791-Sat09Jun2001202431+0300-eliz@is.elta.co.il> from "Eli Zaretskii" at Jun 09, 2001 08:24:32 PM
X-Mailer:	ELM [version 2.5 PL2]
MIME-Version:	1.0
Reply-To:	djgpp-workers AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp-workers AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

According to Eli Zaretskii:
> > 2. Why it annoys me immensly is that I routinely do "cp -a
> > v:/my/cvs/tree/of/djgpp/src/* /djgpp/src.compiling/" while
> > developing. And now I get a ton of warnings from cp because the copy
> > made the previous run of cp is set to readonly.
> 
> When you copy directory trees, you should use "cp -rf".  Otherwise,
> every write-protected file will trigger a prompt.

Not good in this case because then the whole src.compiling tree would
be recompiled even if I'd changed no or only a few files. I need the
flag -p (implied by -a) to preserve the times of the files.


Right,

						MartinS

- Raw text -