Re: retro commits?
Yaron Yogev <[email protected]>
| Newsgroups | gmane.comp.version-control.cvs.general |
|---|---|
| Organization | http://groups.google.com |
| Message-ID | <d7bae319-dcd8-4f42-85fb-1679ef48bb83@y11g2000yqm.googlegroups.com> |
On Aug 25, 2:03 am, Bob Proulx <[email protected]> wrote: > Martin Neitzel wrote: > > Now I want to bring the repository up-to-date by re-doing my commits. > > No problem in that, but if possible I'd like to do that with the > > original commit dates, too. Like RCS's "ci -d" would do. > > > My current plan would be to do a normal "cvs ci" for each change set, > > each followed by manually editing the "date" line in the ,v repository > > file. Is that OK? Has someone else already gone through the required > > motions? > > Personally I would probably commit all of the changes without regards > to the date and then edit the ,v files to update the relevant dates. > That seems reasonable since you say you are already planning on > editing those files. > > Alternatively I would use libfaketime[1] to set the time and do local > commits. You could script it to stat the file and use that timestamp > as the current time. > > Bob > > [1]http://www.code-wizards.com/projects/libfaketime/index.html Hi, Why not use "RCS ci -d" directly on the repository files in the server ? Yaron