Revision: 78307
http://sourceforge.net/p/brlcad/code/78307
Author: starseeker
Date: 2021-02-23 13:30:17 +0000 (Tue, 23 Feb 2021)
Log Message:
-----------
Explain why some of the files are keyed the way they are...
Modified Paths:
--------------
brlcad/trunk/misc/repoconv/NOTES
Modified: brlcad/trunk/misc/repoconv/NOTES
===================================================================
--- brlcad/trunk/misc/repoconv/NOTES 2021-02-22 20:07:17 UTC (rev 78306)
+++ brlcad/trunk/misc/repoconv/NOTES 2021-02-23 13:30:17 UTC (rev 78307)
@@ -331,3 +331,23 @@
http://esr.ibiblio.org/?p=8607
https://gitlab.com/ideasman42/blender-git-migration/
+
+################################################################################
+Note: The files svn_rev_updates.txt, tag_commits.txt, and
branch_corrections.txt
+assume a repository produced by the version of repowork at SVN r76568 (i.e.
+their sha1 keys assume the output produced by the following options at that
+version - newer versions have a processing difference that's not been fixed yet
+that doesn't keep the line between the message and the footer):
+
+./repowork -t -e email_fixups.txt \
+ -n -r cvs_git \
+ -s rev_map \
+ --keymap msgtime_sha1_map --cvs-auth-map key_authormap
--cvs-branch-map key_branchmap \
+ brlcad_raw.fi brlcad_final.fi
+
+This setup isn't ideal: between needing the older revision and the cvs branch
+map assignments setting their incorrect info... Ideally we would just skip
them,
+but it would mean re-keying all of the information in those files to a new set
of
+SHA1 keys manually...
+
+
This was sent by the SourceForge.net collaborative development platform, the
world's largest Open Source development site.
_______________________________________________
BRL-CAD Source Commits mailing list
brlcad-commits@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/brlcad-commits
