Re: Using hash instead of timestamps to check for changes.

2015-04-11 Thread Eric Melski
On 04/11/2015 08:38 AM, Enrico Weigelt, metux IT consult wrote: On 07.04.2015 00:17, Eric Melski wrote: Hi, This problem is relatively common when using an SCM system that preserves *checkin* time on files rather than *checkout* time. I'd consider that a misbehavious of the SCM (IMHO, that's

Re: Using hash instead of timestamps to check for changes.

2015-04-11 Thread Tim Murphy
On 11 April 2015 at 16:38, Enrico Weigelt, metux IT consult < enrico.weig...@gr13.net> wrote: > On 07.04.2015 00:17, Eric Melski wrote: > > > > ClearCase > > does this in various configurations, and Perforce will if your client > > spec has "modtime" set. I'm sure other SCM systems can be setup t

No rule to make target

2015-04-11 Thread Bruce Korb
I am getting this message: make[2]: *** No rule to make target `dep-gnu-pw-mgr.1', needed by `gnu-pw-mgr.1'. Stop. make[2]: Leaving directory `/u/gnu/proj/gnu-pw-mgr-bld/doc' make[1]: *** [all-recursive] Error 1 Seems like a real neophyte problem, but this neophyte has a problem deciphering

Re: No rule to make target

2015-04-11 Thread Bruce Korb
On 04/11/15 11:25, Bruce Korb wrote: I am getting this message: Never mind. I was playing with "$(call ...)" stuff and the text was permuted in an unexpected way...Sorry. ___ Bug-make mailing list Bug-make@gnu.org https://lists.gnu.org/mailman/list

Re: Using hash instead of timestamps to check for changes.

2015-04-11 Thread Enrico Weigelt, metux IT consult
On 07.04.2015 00:17, Eric Melski wrote: Hi, > This problem is relatively common when using an SCM system that > preserves *checkin* time on files rather than *checkout* time. I'd consider that a misbehavious of the SCM (IMHO, that's the reason why Git does not track the mtime). From the filesys