Incremental import of git into darcs
Project description
git-darcs - Incremental import of git into darcs
Just call git-darcs update
, it will import the current git-commit into darcs.
If you get new commits eg. using git pull
, you can call git-darcs update
and
it will import each commit into darcs. git-darcs will walk a truly linear
git-history, but it has some caveats. See: Linearized history
By default the first import is shallow, only importing the current git-commit.
If you want to import the whole history use git-darcs update --no-shallow
,
since we linearize the history by checking out each commit this can take
very long.
On the first import you can also supply a custom base-commit git-darcs update --base fa2b982
ignoring history you are not interested in.
The options base
and shallow
are ignored after the first import.
Use a global gitignore
to ignore _darcs
in all your depositories.
With git-darcs clone <source> <destination>
you can clone a darcs/git dual
repository locally. Both git and darcs will make sure no history-data is
duplicated on disk.
The tool is intentionally very minimal, it is for devs. They can read tracebacks
or change the code to fit better. To create git patches from my
working-repositories I use darcs rebase suspend
and git commit -a -v
.
But why
I prefer to group changes by topic, so I am constantly amending patches. This is
very easy in darcs and more complicated in git. Yes, I know about --fixup
and
--autosquash
in git. Also I can find independent low-risk patches easily with
darcs show dependencies
, so I can constantly make PRs. Making the final
breaking change/PR much smaller. This is less tedious for the reviewers.
For darcs beginners
- There is a great video by raichoo the maintainer of hikari
- You have to read the darcs book, you just have to
_darcs/pref/boring
is the equivalent of.gitignore
, but has quite a wide definition of boring by default
Darcs does not handle chmod
or symbolic-links. The easiest way to workaround
this, is letting git
do the work. I have two git/darcs repositories for each
project.
project
(the repository I work in) containing a.git
and a_darcs
project-tracking
(the repository that tracks changes from upstrream, also containing a.git
and a_darcs
I then pull new darcs-patches from project-tracking
into project
. Once my
the changes are in upstream, I obliterate everything to the checkpoint (tag) I
started with and pull the patches (now via git
) from project-tracking
. Or I
remove project
and clone it again from project-tracking
.
Since I always make git-commits from the darcs-patches git
will track chmod
and symbolic-links for me.
Usage
Note: this asciinema was made before shallow
was default.
$> git-darcs --help
Usage: git-darcs [OPTIONS] COMMAND [ARGS]...
Click entrypoint.
Options:
--help Sow this message and exit.
Commands:
clone Locally clone a tracking repository to get a working-repository.
update Incremental import o git into darcs.
$> git-darcs update --help
Usage: git-darcs update [OPTIONS]
Incremental import of git into darcs.
By default it imports a shallow copy (the current commit). Use `--no-
shallow` to import the complete history.
Options:
-v, --verbose / -nv, --no-verbose
-w, --warn / -nw, --no-warn Warn that repository will be cleaned
-b, --base TEXT On first update import from (commit-ish)
-s, --shallow / -ns, --no-shallow
On first update only import current commit
--help Show this message and exit.
$> git-darcs clone --help
Usage: git-darcs clone [OPTIONS] SOURCE DESTINATION
Locally clone a tracking repository to get a working-repository.
Options:
-v, --verbose / -nv, --no-verbose
--help Show this message and exit.
Linearized history
If the history forks git-darcs will walk the history-branch offered by git rev-list --topo-order
. It will try to fast-forward every revision it gets into
the current revision. On the 'main' branch this will always work, so it will
record all these revisions. On the other branches (of the history) this will
fail and it will skip all these revisions, until the branches merge again and
fast-forward is possible.
git-darcs will track any moves that happened when skipping revisions so all these moves will get recorded. It will add the complete log of the skipped revisions into the patch that records all these changes.
This git-history:
$> git log --oneline --graph
* 74b2d99 (HEAD -> master) end > end0
* 9de72f8 end
* a5f4bfb Merge branch 'b'
|\
| * 9c5e6c4 (b) bc, start1b1 > start1b2, ba0 > ba1, bb > bb0
| * 00781ed bb, start1b0 > start1b1, ba > ba0
| * 259f647 ba, start1 > start1b0
* | deab3ea start_merged > start_merged1
* | de04805 Merge branch 'a'
|\ \
| * | 1e6f333 (a) ac, start1a1 > start1a2, aa0 > aa1, ab > ab0
| * | 63ccd72 aa, start1a0 > start1a1, aa > aa0
| * | a28638c aa, start1 > start1a0
| |/
* / c64713f start1 > start2
|/
* 83c267b start0 > start1
* 712ec2d start > start0
* 44d8cd1 start
becomes this darcs-history Note that the moves correspond to the moves I logged,
there is never a rmfile
or a move
in the wrong direction. Here darcs
couldn't record branch a
or b
so all the changes appear in the patches
corresponding to the merge-commits.
* 74b2d99 end > end0
move ./end ./end0
* 9de72f8 end
addfile ./end
* a5f4bfb Merge branch 'b'
9c5e6c4 bc, start1b1 > start1b2, ba0 > ba1, bb > bb0
00781ed bb, start1b0 > start1b1, ba > ba0
259f647 ba, start1 > start1b0
move ./start_merged1 ./start
addfile ./ba1
addfile ./bb0
addfile ./bc
* deab3ea start_merged > start_merged1
move ./start_merged ./start_merged1
* de04805 Merge branch 'a'
1e6f333 ac, start1a1 > start1a2, aa0 > aa1, ab > ab0
63ccd72 aa, start1a0 > start1a1, aa > aa0
a28638c aa, start1 > start1a0
move ./start2 ./start_merged
addfile ./aa1
addfile ./ab0
addfile ./ac
* c64713f start1 > start2
move ./start1 ./start2
* 83c267b start0 > start1
move ./start0 ./start1
* 712ec2d start > start0
move ./start ./start0
* 44d8cd1 start
addfile ./start
However if we remove the commit that prevented fast-forward, we get this git-history:
$> git log --oneline --graph
* 4d57edd (HEAD -> master) end > end0
* 6526a18 end
* f4facb0 Merge branch 'b'
|\
| * 9c5e6c4 (b) bc, start1b1 > start1b2, ba0 > ba1, bb > bb0
| * 00781ed bb, start1b0 > start1b1, ba > ba0
| * 259f647 ba, start1 > start1b0
* | 1e6f333 (a) ac, start1a1 > start1a2, aa0 > aa1, ab > ab0
* | 63ccd72 aa, start1a0 > start1a1, aa > aa0
* | a28638c aa, start1 > start1a0
|/
* 83c267b start0 > start1
* 712ec2d start > start0
* 44d8cd1 start
Again, there are no rmfile
or move
in the wrong direction, but it could
record the changes on branch a
.
* 4d57edd end > end0
move ./end ./end0
* 6526a18 end
addfile ./end
* f4facb0 Merge branch 'b'
9c5e6c4 bc, start1b1 > start1b2, ba0 > ba1, bb > bb0
00781ed bb, start1b0 > start1b1, ba > ba0
259f647 ba, start1 > start1b0
move ./start1a2 ./start1_merged
addfile ./ba1
addfile ./bb0
addfile ./bc
* 1e6f333 ac, start1a1 > start1a2, aa0 > aa1, ab > ab0
move ./aa0 ./aa1
move ./ab ./ab0
move ./start1a1 ./start1a2
addfile ./ac
* 63ccd72 aa, start1a0 > start1a1, aa > aa0
move ./aa ./aa0
move ./start1a0 ./start1a1
addfile ./ab
* a28638c aa, start1 > start1a0
move ./start1 ./start1a0
addfile ./aa
* 83c267b start0 > start1
move ./start0 ./start1
* 712ec2d start > start0
move ./start ./start0
* 44d8cd1 start
addfile ./start
Project details
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Built Distribution
Hashes for git_darcs-0.6.0-py3-none-any.whl
Algorithm | Hash digest | |
---|---|---|
SHA256 | 60ca6dc546f222280221b18fdfac2ba35ddc88bab0eff0333969e937a440502c |
|
MD5 | 7ef0e79d5ded182344b280cd4e1f070a |
|
BLAKE2b-256 | a33b62e56da9484b2d3d84bc3068cd990d7d3783494fb086667f81c219a3fe01 |