Issue 2428 incremental convert import into an existing repo

Title incremental convert import into an existing repo
Priority wishlist Status unknown
Milestone Resolved in
Superseder Nosy List bf, gh
Assigned To gh
Topics Git

Created on 2015-01-23.22:06:31 by bf, last changed 2017-07-31.02:11:00 by gh.

File name Uploaded Type Edit Remove
feature_-allow-darcs-convert-import-in-an-existing-darcs-repo.dpatch bf, 2015-01-23.22:08:24 application/x-darcs-patch
msg17944 (view) Author: bf Date: 2015-01-23.22:06:29
Darcs should be able to import from e.g. a git repo in an incremental
manner. There is not much that needs to be done for that: we merely need
to lift the restriction that darcs convert import must create a new
repository. A very simple 5 line change (attached) is enough to lift
this restriction; however, the resulting repo has no working tree. This
is probably very easy to fix for someone who knows more about the internals.

Also when the stream is from a git repo, there are these extra

Author: Anonymous Tagger <>
Date:   Thu Jan  1 01:00:00 CET 1970
  tagged refs/heads/master

patches (tags) that should not be there IMHO, at least not twice(!) per
import. Fortunately one can just obliterate these tags, so no harm done
unless one forgets and puts darcs tags on top of them. An option to
filter this trash out would be nice.
msg17945 (view) Author: bf Date: 2015-01-23.22:08:24
Oops, forgot to attach the patch, here we go.
Date User Action Args
2015-01-23 22:06:31bfcreate
2015-01-23 22:08:25bfsetfiles: + feature_-allow-darcs-convert-import-in-an-existing-darcs-repo.dpatch
messages: + msg17945
2015-02-02 22:46:31bfsetpriority: feature -> wishlist
2016-01-21 12:21:08ghsettopic: + Git
2017-07-31 02:11:00ghsetassignedto: gh
nosy: + gh