<?xml version="1.0" encoding="ISO-8859-1"?>

<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
	<channel>
		<title>SVNForum.org - Subversion Forum - Version Control Practices</title>
		<link>http://www.svnforum.org/</link>
		<description><![CDATA[Subversion concepts, including Branching, Merging & Repository management Best Practices.]]></description>
		<language>en</language>
		<lastBuildDate>Wed, 22 May 2013 18:30:28 GMT</lastBuildDate>
		<generator>vBulletin</generator>
		<ttl>60</ttl>
		<image>
			<url>http://www.svnforum.org/images/misc/rss.png</url>
			<title>SVNForum.org - Subversion Forum - Version Control Practices</title>
			<link>http://www.svnforum.org/</link>
		</image>
		<item>
			<title>No merge conflict for deleted folder</title>
			<link>http://www.svnforum.org/threads/51630-No-merge-conflict-for-deleted-folder?goto=newpost</link>
			<pubDate>Sat, 11 May 2013 18:58:10 GMT</pubDate>
			<description>Baseline: 
 
* BranchA - FolderA contains FileA 
* BranchB branch from BranchA 
 
 
 
Commits: 
 
* BranchA - FileA move out of FolderA to root</description>
			<content:encoded><![CDATA[<div>Baseline:<br />
<ul><li style="">BranchA - FolderA contains FileA</li><li style="">BranchB branch from BranchA</li></ul><br />
<br />
Commits:<br />
<ul><li style="">BranchA - FileA move out of FolderA to root</li><li style="">BranchA - FolderA deleted</li><li style="">BranchB - FileA modified</li></ul><br />
<br />
If I merge BranchA into BranchB I will not get any merge conflict. In BranchB the FolderA is deleted and FileA is not modified and I have miss the changed in FileA done in BranchB. Even If I have done the changes in BranchA in 1 or 2 commit the result is the same.<br />
<br />
If I merge BranchB into BranchA I will get a merge conflict as expected.<br />
<br />
What is best pratices about this merge situation?</div>

]]></content:encoded>
			<category domain="http://www.svnforum.org/forums/26-Version-Control-Practices">Version Control Practices</category>
			<dc:creator>chitech</dc:creator>
			<guid isPermaLink="true">http://www.svnforum.org/threads/51630-No-merge-conflict-for-deleted-folder</guid>
		</item>
		<item>
			<title>Tag Revision Number</title>
			<link>http://www.svnforum.org/threads/51305-Tag-Revision-Number?goto=newpost</link>
			<pubDate>Tue, 07 May 2013 02:00:59 GMT</pubDate>
			<description><![CDATA[Hi Guys, 
 
I'm using TortoiseSVN 1.7.11, Build 23600 - 64 Bit , 2012/12/12 19:08:52 client and I have a question about tagging and the revision...]]></description>
			<content:encoded><![CDATA[<div>Hi Guys,<br />
<br />
I'm using TortoiseSVN 1.7.11, Build 23600 - 64 Bit , 2012/12/12 19:08:52 client and I have a question about tagging and the revision number assigned to the tagged copy.<br />
<br />
In my Repo setup I have a Development section and a Deployed section.<br />
Once the code is tested and released to the customer I Tag a copy to the Deployed section.<br />
I want the Deployed Copy to display the same Revision number as the Head Revision as they are the same at the time of deployment.<br />
<br />
I have previously done this with an older version of Tortoise but with the current version of Tortoise it seems to increment the revision of the deployed tagged copy when viewed with the Repo browser.<br />
<br />
Any advice on how to Tag and maintain the revision number would be appreciated.<br />
<br />
Thanks,<br />
<br />
Red.</div>

]]></content:encoded>
			<category domain="http://www.svnforum.org/forums/26-Version-Control-Practices">Version Control Practices</category>
			<dc:creator>Red Diablo</dc:creator>
			<guid isPermaLink="true">http://www.svnforum.org/threads/51305-Tag-Revision-Number</guid>
		</item>
	</channel>
</rss>
