Here a fix to handle the dry-run vs dry_run and the install of
the repository directory:
diff -rN -u old-tailor/setup.py new-tailor/setup.py
--- old-tailor/setup.py 2006-06-29 04:07:51.0 +0200
+++ new-tailor/setup.py 2006-06-29 04:07:51.0 +0200
@@ -7,7 +7,7 @@
Fri Jun 30 00:38:26 CEST 2006 [EMAIL PROTECTED]
* [git] Improve error cases when importing branches
This patch creates a new exception to identify the case where the user made
an error
when specifying a branchpoint parameter, and does an explicit check to
abort when
attempting to
Fri Jun 30 01:51:02 CEST 2006 [EMAIL PROTECTED]
* [git] Preserve initial commit msg on branch in repository mode as well
The criteria to detect if we are dealing with a branch is the existence
of the branchpoint parameter, regardless of the way we import branches
(multi-repo or
#64: cvs - bzr conversion fails on adding files to non-existent directories
Heh, casually I run into this today as well.
Attached a patch to fix this in the Bzr target, but I'm not sure at all if
it's the right place. Perhaps it could be fixed in the CVS source?
This patch adds yet another
* Adeodato Simó [Fri, 30 Jun 2006 04:37:57 +0200]:
This patch adds yet another loop of processing to bzr's _addPathnames(),
all because WorkingTree.add() is used to talk to bzrlib, instead of
smart_add_tree().
[...]
#64 would get solved with this, and I'd say it'd be possible to simplify
a
Attached is a patch doing this:
Forgot to say: that assumes that arguments to _addPathnames and
_addSubtree are always relative to the root of the repository, and never
absolute path. Is this assumption correct?
Thanks,
--
Adeodato Simó dato at
