Re: auto-merge into sparse checkout branch - new files added
From: <bjc_tsvn_at_btinternet.com>
Date: Mon, 23 Jan 2017 16:15:08 +0000 (UTC)
Hi,
>> using auto-merge via MRoR with revision range blank.<<
Have a look at http://svnbook.red-bean.com/en/1.7/svn.branchmerge.basicmerging.html. The "Keeping a Branch in Sync" section, describes the process of merge, review status, commit, and finally updating the local checkout.
On Monday, 23 January 2017, 15:55, Charles Wilt <charles.wilt_at_gmail.com> wrote:
I'm new to SVN and just completed my first merge of the trunk into my feature branch; using auto-merge via MRoR with revision range blank.
It completed successfully and I see what I expected to with the exception that new files that been added to trunk are now showing in the working copy of my branch with a status of "added"
As I considered it, I realize this behavior makes perfect sense.
However, my branch working copy was created via a sparse checkout. I don't want or need the newly added items for my work.
So two questions:
Is there some option that will prevent newly added items from being added to my sparse checkout unless I specifically cherry pick them?
I'm using TortiseSVN 1.9.4
Thanks!
------------------------------------------------------
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
------------------------------------------------------
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
|
This is an archived mail posted to the TortoiseSVN Users mailing list.
This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.