<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://wiki.multitheftauto.com/wiki/Talk:Git_Coding_Guidelines?action=history&amp;feed=atom</id>
	<title>Talk:Git Coding Guidelines - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://wiki.multitheftauto.com/wiki/Talk:Git_Coding_Guidelines?action=history&amp;feed=atom"/>
	<link rel="alternate" type="text/html" href="https://wiki.multitheftauto.com/index.php?title=Talk:Git_Coding_Guidelines&amp;action=history"/>
	<updated>2026-05-18T19:47:47Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.39.3</generator>
	<entry>
		<id>https://wiki.multitheftauto.com/index.php?title=Talk:Git_Coding_Guidelines&amp;diff=21510&amp;oldid=prev</id>
		<title>Ccw: Problem with the current model</title>
		<link rel="alternate" type="text/html" href="https://wiki.multitheftauto.com/index.php?title=Talk:Git_Coding_Guidelines&amp;diff=21510&amp;oldid=prev"/>
		<updated>2009-09-12T10:47:49Z</updated>

		<summary type="html">&lt;p&gt;Problem with the current model&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;=Problem with the current model.=&lt;br /&gt;
&lt;br /&gt;
In the current system, changes could be in 'merge' which may not end up in 'untested' for a long time. This will&lt;br /&gt;
disrupt read access to the code that exists beyond merge. An extreme example would be where a change in 'merge' deleted or renamed files.&lt;br /&gt;
&lt;br /&gt;
A solution would be to keep the future stuff in branches above 'merge'. Perhaps in logical sections, a bit like the branching that was done with SVN. (See diagram)&lt;br /&gt;
[[File:Gittree88.png]]&lt;br /&gt;
[[user:ccw|ccw]] 12:46, 12 September 2009&lt;/div&gt;</summary>
		<author><name>Ccw</name></author>
	</entry>
</feed>