[PATCH 0 of 2] document convert-repo interfaces
Edouard Gomez
ed.gomez at free.fr
Mon May 21 21:50:10 UTC 2007
On Sun, 20 May 2007 18:12:26 +0200, Thomas Arendsen Hein wrote:
> What about migrating convert-repo into an hg extension? This way we get
> the help system for free.
Working on it right now. Does an UI like that fits your wish ?
hg convert [same options as my patched convert-repo]
>> I've put on my site an updated queue, have a look at it and don't
>> hesitate giving feedback.
>> http://ed.gomez.free.fr/mercurial/convert-repo-queue.tar.bz2
>
> I've looked at that, your patches don't include # HG header, so on
> imports the committer name would be lost.
For my patches i wouldn't care losing authorship.
And once everything gets ACK i will have submit a clean hg export of all
patches, respecting authorship of patches i would not have written.
> Regarding ./generic/enh-init-dst-after-src.patch: In which situation
> will an empty/broken hg target repo exist? With a non-existing source
> name and an empty source dir the target repo doesn't exist when using
> "convert-repo foo".
Because the previous patch enh-dst-repo-init.patch detects a case that
the current one doesn't catch that is:
- doesn't init a non empty dir that is not a mercurial repo already.
So i thought it could be good not to init the src repo if the dst repo is
not able to hold the conversion. The patch didn't prove useful, but
afterwards, in the case of svn, convert.svn__init__ is not cheap, so
avoiding it is quite cool.
This patch can be trashed if you want.
--
Edouard Gomez
More information about the Mercurial-devel
mailing list