Files
JIMRI/help/en/html/doc/Technical/SVNFAQ.shtml
T
2026-06-17 14:00:51 +02:00

53 lines
1.9 KiB
Plaintext

<!DOCTYPE html>
<html lang="en">
<head>
<meta name="generator" content="HTML Tidy for HTML5 for Apple macOS version 5.8.0">
<title>JMRI: Subversion FAQ</title>
<meta name="author" content="Bob Jacobsen">
<meta name="keywords" content="JMRI technical code SVN Subversion FAQ">
<!--#include virtual="/help/en/parts/Style.shtml" -->
</head>
<body>
<!--#include virtual="/help/en/parts/Header.shtml" -->
<div id="mBody">
<!--#include virtual="Sidebar.shtml" -->
<div id="mainContent">
<h1>JMRI Code: Subversion FAQ</h1>
<p class="important">JMRI has migrated from Subversion (SVN) to Git in September 2015. For
our current Version Control FAQ, please see the <a href="GitFAQ.shtml">Git FAQ</a>.</p>
<p>This is a list of Frequently Asked Questions for Subversion, particularly regarding how we
used it with JMRI up until 2015.</p>
<p>See also the <a href="index.shtml">Technical index</a> for more information on maintaining
JMRI code.</p>
<h3>SVN Properties</h3>
In general, we keep everything in SVN revision control, so there's no need for the various
properties lines we used to need in CVS. These looked like
<pre>
# The next line is maintained by CVS, please don't change it
# $Revision$
</pre>
<p>But there are certain files, like decoder XML, properties files, etc, that users are
likely to edit and submit back for inclusion. It is very helpful if we can identify the
specific content that they started with.</p>
<p>Therefore, for html, XML, python and properties files, we do:</p>
<pre>
svn propset svn:keywords "Date Revision Version Id Author" {}
</pre>That way SVN will fill in those tags if/when they're present and the file is changed.
<!--#include virtual="/help/en/parts/Footer.shtml" -->
</div>
<!-- closes #mainContent-->
</div>
<!-- closes #mBody-->
<script src="/js/help.js"></script>
</body>
</html>