version control - How can I merge SVN branches into my trunk without losing commit messages and author details -
our svn repository works follows:
- nothing can committed trunk unless passes qa (trunk "releasable")
- development work done on branches last approximately 30 days , reintegrated trunk (after qa of course)
the problem approach commits branches developers end looking single huge commit on trunk single developer (the 1 did merge).
my question is:
is there way improve this? other version control systems better job @ maintaining logs? ones?
i'm not interested in having commit trunk , branching each release. did number of years , doesn't work us. need maintain concurrent development branches , need have ability release on short notice.
with merge tracking (as of subversion 1.5) can see revisions produced code later merged. see http://tortoisesvn.net/docs/release/tortoisesvn_en/tsvn-dug-showlog.html#tsvn-dug-showlog-mergetrack describes problem.
Comments
Post a Comment