hi larry,
oops, I couldn't find a -d option in cvs' info docus. Perhaps it's still
not supported in 1.11.5?!
It's mentioned in the Quick Reference, but not in the detailed guide.
It's not new, it's been there forever.
thanks for the hint. Strange that it isn't visible in the info manual!
marko wrote:
Anyway, as I see now there doesn't seem to be a comparable
option for the
add command, though. Only import would allow this, add won't!
Am I right? If so, it would be quite strange...
The option is not there *because* it is not a good idea to do this.
Marko, let me repeat what
Hi Larry,
On Thu, 8 Jul 2004, Larry Jones wrote:
If you mean you want checkout to record the current timestamp of the
file rather than the time of the checkin, that would also break things
like make. Import, however, has the -d option to do just that.
oops, I couldn't find a -d option in
marko writes:
oops, I couldn't find a -d option in cvs' info docus. Perhaps it's still
not supported in 1.11.5?!
It's mentioned in the Quick Reference, but not in the detailed guide.
It's not new, it's been there forever.
-Larry Jones
I like maxims that don't encourage behavior
Hi,
I wonder how CVS can be convinced to set the original date/time of a file
at checkin time when I do a checkout!
Marko
___
Info-cvs mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/info-cvs
At 12:56 PM 7/8/2004, marko wrote:
I wonder how CVS can be convinced to set the original date/time of a file
at checkin time when I do a checkout!
Use the Source!
But, really. Do you want to do that? Do you expect to use make?
Fred
___
marko writes:
I wonder how CVS can be convinced to set the original date/time of a file
at checkin time when I do a checkout!
I'm having a hard time parsing that sentence, but I think that's what it
already does -- when you do a fresh checkout, the files have the
timestamps of when they were
[EMAIL PROTECTED] wrote:
If you mean you want checkout to record the current timestamp of the
file rather than the time of the checkin, that would also break things
like make.
I'm not sure I follow this. How would using the timestamp of the file
instead of the time of checkin break make?
--- Forwarded mail from [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
If you mean you want checkout to record the current timestamp of the
file rather than the time of the checkin, that would also break things
like make.
I'm not sure I follow this. How would using the timestamp of the file
[EMAIL PROTECTED] wrote:
I'm not sure I follow this. How would using the timestamp of the file
instead of the time of checkin break make?
The problem is that the CVS doesn't guarantee that the files
are copied
into the workspace in the same order in which they were
checked in. So
for
Jim.Hyslop wrote:
[EMAIL PROTECTED] wrote:
I'm not sure I follow this. How would using the timestamp of the file
instead of the time of checkin break make?
The problem is that the CVS doesn't guarantee that the files
are copied
into the workspace in the same order in which they were
Derek R. Price writes:
It wouldn't, but it could break the RCS archive file contract that says
that internal commit timestamps will be increasing.
Is there such a contract, given that RCS's ci has a -d option that lets
you set the date to anything you want (and its default is the file's
Larry Jones wrote:
Derek R. Price writes:
It wouldn't, but it could break the RCS archive file contract that says
that internal commit timestamps will be increasing.
Is there such a contract, given that RCS's ci has a -d option that lets
you set the date to anything you want (and its
Derek R. Price wrote:
Yes. RCS_getdatebranch() in rcs.c stops when it finds the first date
that is too old. From RCS_getdatebranch() in rcs.c:
Of course, this doesn't necessarily mean that that can't be fixed, but
any archive file that took advantage of it would no longer work quite
14 matches
Mail list logo
