Question about Branching/Merging practices
From: Lars Grunewaldt <lgw_at_dark-reality.de>
Date: Thu, 13 Mar 2008 12:02:01 +0100
-----BEGIN PGP SIGNED MESSAGE-----
Hi there,
I have a problem with a specific "use case" of subversion, considering
But in my current working environment with more than 10 developers
1. we reach a point where we need to branch from trunk for a second
2. while those 2nd branch is "in the works", there where some bugfixes
3. we decide that we need those bugfixes *immediatly* in the branch,
branch_wd:> svn commit
4. so far so good. The branch continues, and we finally reach
5. now we want to merge all changes from the branch back to trunk:
trunk_wd:> svn merge -r100:140 svn://branch
Wupps: this will lead to some conflicts, because we will actually
But what can be done to avoid this? Is there a possibility to somehow
Should we do two merges, like:
svn merge -r100:110 svn://branch
which would obviously ignore the merged changes from trunk, but leads
With best regards,
- --
-----BEGIN PGP SIGNATURE-----
iD8DBQFH2QmpISCS20rPIYsRApbsAJwL076UsiWryXYvFbuwzgSvpphgCwCfUa4n
---------------------------------------------------------------------
|
This is an archived mail posted to the Subversion Users mailing list.
This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.