Fabien Costantini wrote:
> So beware of copy between to revisions, it may not work as expected.
Okay, that explains it.
> I will add a test directory (src_doc in documentation) then will commit and
> then will test locally again if svn move this time will keep history.
I wouldn't try it on the real branch, better use another test branch. And the
best would be to use a local repository (it's easy to create one with file:
access on a local pc, and play with that).
I already tried a similar thing, and it appeared that you can't do svn log on
the
new {copied|moved} files before you commit the change (IIRC).
> I currently test with r6430 just to validate the principle locally, it is
> then possible to make a backup of current .dox changes Doxyfile Makefile,
> revert to r6430, apply the new patches will all modifications, commit this
> new version ?
I don't know if I understood that correctly, but:
(1) I think that you can't use an old version on a working copy and then commit
changes to the head version (svn will ask you to update first).
(2) It's not only the *.dox files, but also all the image files.
But if you find a way...
Albrecht
_______________________________________________
fltk-dev mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk-dev
