Hi,
On Sun, Aug 13, 2006 at 02:01:06PM -0400, Kevin Smith
wrote:> Can you confirm that merging between branches within an svn repository
> works well? The article implies that it does not.
It does not. SVN does not record ANY meta-information for merges. After
the merge the merge-commit is not distinguishable from any other commit.
Merging repeatedly from one branch to another is kludgy if you forgot
your last "merge-point" (and forgot to note it in your last
merge-commit).
Even the Subversion book admits[1]:
"Ideally, your version control system should prevent the
double-application of changes to a branch. It should automatically
remember which changes a branch has already received, and be able to
list them for you. It should use this information to help automate
merges as much as possible.
Unfortunately, Subversion is not such a system. Like CVS, Subversion
does not yet record any information about merge operations. When you
commit local modifications, the repository has no idea whether those
changes came from running svn merge, or from just hand-editing the
files."
I find that unacceptable for my personal work and only use SVN when I''m
forced to. SVK adds meta-infos about merges and also has an
implementation of tla''s star-merge, but for it to work reliable
everybody doing merges in the repository must use SVK.
Greetings, Tobi
[1]
http://svnbook.red-bean.com/en/1.2/svn.branchmerge.copychanges.html#svn.branchmerge.copychanges.bestprac
--
GPG-Key 0xE2BEA341 - signed/encrypted mail preferred
My, oh so small, homepage: http://portfolio16.de/
http://www.fli4l.de/ - ISDN- & DSL-Router on one disk!
Registered FLI4L-User #00000003
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url :
http://rubyforge.org/pipermail/wxruby-users/attachments/20060814/2e97ef82/attachment.bin