Differences

This shows you the differences between two versions of the page.

--- versioncontrol:signing [2007/09/20 20:57] – GordonTetlow
+++ versioncontrol:signing [2022/10/07 02:02] (current) – Move bakeoff stuff under a single namespace KubilayKocak
@@ Line 6: / Line 6: @@
 ===== SVN Implementation =====
+A post-commit hook can make whatever signatures you like.  The change files are immutable once committed to the repository.  Note that a manual obliterate will destroy signatures as the dump/restore will recreate inter-commit delta linkage.  Signatures would graphically highlight an obliterate.
 ===== Hg Implementation =====
@@ Line 11: / Line 13: @@
 There is a standard extension (plugin) for gpg support.  It creates a version-controlled file called ''%%.hgsigs%%'' in the root which does for signing what ''%%.hgtags%%'' does for tags: it inserts a changeset recording the signature of a given changeset so it is more signing a repository/release than a one-sig-per-file implementation.
-I've not checked it but it may have the same problem as git with ["%%VCSFeatureObliterate%%"].
+I've not checked it but it may have the same problem as git with [[/VCSFeatureObliterate|VCSFeatureObliterate]].
 ===== Git Implementation =====
@@ Line 20: / Line 22: @@
 </code>
-Note that this is in conflict with ["%%VCSFeatureObliterate%%"]!
+Note that this is in conflict with [[/VCSFeatureObliterate|VCSFeatureObliterate]]!
 ===== Monotone Implementation =====
 **Supported**
-(also see [http://venge.net/monotone/wiki/FeatureSignedRevisions monotone:[[/FeatureSignedRevisions|FeatureSignedRevisions]]])
+(also see [[http://venge.net/monotone/wiki/FeatureSignedRevisions|monotone:FeatureSignedRevisions]])
 This is a primary and fundamental component of monotone. Revisions are identified by the SHA-1 hash of their ancestry+content, and additional metadata about these revisions is attached using signed certs.