[Svnmerge] Which version should I use?

Giovanni Bajo rasky at develer.com
Tue Oct 4 03:29:31 PDT 2005


Archie Cobbs <archie at dellroad.org> wrote:

>> Is there a plan to centralize on one version? I'm afraid that the cost
>> of maintaining two different ports of different languages of the same
>> codebase is going to result in bugs in both and a set of features spread
>> across both that would be useful but neither fully implement.
>
> The python version is newer and less stable but is being more
> actively developed. Eventually we'll probably revert to it being
> the only version once it's been tested a little more... as always,
> code speaks louder than words :-)

Also, the python version has some new experimental features that have been
discussed in the mailing list in the past weeks. The ChangeLog is:

# - Add support for more informative commit message (-V).
# - Add double-verbose mode, which shows every svn command executed (-v -v)
# - "svnmerge avail" now only shows commits in head, not also commits in
other
#   parts of the repository.
# - Add "svnmerge block" to flag some revisions as blocked, so that they
#   will not show up anymore in the available list. Added also the
#   complementary "svmerge unblock". "svnmerge avail" has grown two new
options:
#   -B to display a list of the blocked revisions; -A to display both the
#   the blocked and the available revisions.

Testing is really appreciated, btw :)
-- 
Giovanni Bajo




More information about the Svnmerge mailing list