https://sourceforge.net/p/mediacompanion/wiki/OpenSourceTerms/Recent changes to OpenSourceTermsenTue, 23 May 2017 02:08:34 -0000https://sourceforge.net/p/mediacompanion/wiki/OpenSourceTerms/<div class="markdown_content"><h1 id="open-source-terms">Open Source Terms</h1> <ul> <li><strong>Source Code</strong> - source code is text written in a computer programming language.</li> <li><strong>Repository</strong> - The repository contains the history of your project</li> </ul> <blockquote> <blockquote> <p><a href="http://mercurial.selenic.com/wiki/Repository" rel="nofollow">http://mercurial.selenic.com/wiki/Repository</a></p> </blockquote> </blockquote> <ul> <li><strong>Working Directory</strong> - The working directory is the top-level directory in a repository, in which the plain versions of files are available to read, edit and build.</li> </ul> <blockquote> <blockquote> <p><a href="http://mercurial.selenic.com/wiki/WorkingDirectory" rel="nofollow">http://mercurial.selenic.com/wiki/WorkingDirectory</a></p> </blockquote> </blockquote> <ul> <li><strong>Branch</strong> - Branches occur if lines of development diverge. The term "branch" may thus refer to a "diverged line of development". For Mercurial, a "line of development" is a linear sequence of consecutive changesets. Combining a line of development into an existing one is called merging.</li> </ul> <blockquote> <blockquote> <p><a href="http://mercurial.selenic.com/wiki/Branch" rel="nofollow">http://mercurial.selenic.com/wiki/Branch</a></p> </blockquote> </blockquote> <ul> <li><strong>Change Set</strong> - is a collection of changes to files in a source code repository</li> </ul> <blockquote> <blockquote> <p><a href="http://mercurial.selenic.com/wiki/ChangeSet" rel="nofollow">http://mercurial.selenic.com/wiki/ChangeSet</a></p> </blockquote> </blockquote> <ul> <li><strong>Merging</strong> - A merge combines two separate changesets in a repository into a merge changeset that describes how they combine. Merging is the process of joining points on two branches into one, usually at their current heads.</li> </ul> <blockquote> <blockquote> <p><a href="http://mercurial.selenic.com/wiki/Merge" rel="nofollow">http://mercurial.selenic.com/wiki/Merge</a></p> </blockquote> </blockquote> <ul> <li><strong>Tip</strong> - "tip" is a built-in tag referring to the latest changeset created, either by "hg commit" or "hg pull". Use "hg tip" to see the tip's log entry.</li> </ul> <blockquote> <blockquote> <p><a href="http://mercurial.selenic.com/wiki/Tip" rel="nofollow">http://mercurial.selenic.com/wiki/Tip</a></p> </blockquote> </blockquote> <ul> <li><strong>Head</strong> - A head is a changeset with no child changesets. The tip is the most recently changed head. Other heads are recent pulls into a repository that have not yet been merged.</li> </ul> <blockquote> <blockquote> <p><a href="http://mercurial.selenic.com/wiki/Head" rel="nofollow">http://mercurial.selenic.com/wiki/Head</a></p> </blockquote> </blockquote> <ul> <li><strong>Fork</strong> - a project fork happens when developers take a copy of source code and start independent development on it, creating a distinct piece of software. Often a fork is used to try a new feature &amp; see if it pans out. If it does, it can be merged with the main program later on by a <em>Project Owner only</em>.</li> </ul> <blockquote> <blockquote> <p><a href="http://blogs.msdn.com/b/codeplex/archive/2010/03/05/codeplex-mercurial-support-for-forks.aspx" rel="nofollow">http://blogs.msdn.com/b/codeplex/archive/2010/03/05/codeplex-mercurial-support-for-forks.aspx</a></p> </blockquote> </blockquote> <ul> <li><strong>Commit</strong> - The act of creating a changeset is called a commit</li> </ul> <blockquote> <blockquote> <p><a href="http://mercurial.selenic.com/wiki/Commit" rel="nofollow">http://mercurial.selenic.com/wiki/Commit</a></p> </blockquote> </blockquote></div>RobTue, 23 May 2017 02:08:34 -0000https://sourceforge.net802cb4125c8f482f8cf4a48a70e3fc8d73c88943