back-trace using transplant extension

Steve Borho steve at borho.org
Tue Nov 28 07:35:48 CST 2006


Hello,

I've been trying out the new transplant extension that just made it into crew.
It seems to work as expected so long as I provide a revision number for it to
cherry pick.  However, if I leave off the rev id I get this back-trace:

steve at mre> hg transplant -s ../test
searching for changes
warning: repository is unrelated
** unknown exception encountered, details follow
** report bug details to http://www.selenic.com/mercurial/bts
** or mercurial at selenic.com
** Mercurial Distributed SCM (version 199dcb97a5b6)
Traceback (most recent call last):
  File "/home/steve/bin/hg", line 12, in ?
    commands.run()
  File "/home/steve/lib/python/mercurial/commands.py", line 2741, in run
    sys.exit(dispatch(sys.argv[1:]))
  File "/home/steve/lib/python/mercurial/commands.py", line 2964, in dispatch
    return d()
  File "/home/steve/lib/python/mercurial/commands.py", line 2923, in <lambda>
    d = lambda: func(u, repo, *args, **cmdoptions)
  File "/home/steve/lib/python/hgext/transplant.py", line 537, in transplant
    revs, newmerges = browserevs(ui, source, alltransplants, opts)
  File "/home/steve/lib/python/hgext/transplant.py", line 368, in browserevs
    displayer = commands.show_changeset(ui, repo, opts)
  File "/home/steve/lib/python/mercurial/demandload.py", line 71, in __getattribute__
    return getattr(module, key)
AttributeError: 'module' object has no attribute 'show_changeset'


This seems to occur irregardless of whether the source repo is
related to the target or not.

-- 
Steve Borho (steve at borho.org)


More information about the Mercurial-devel mailing list