#181: Non-trivial unmarked branching
------------------------------+---------------------------------------------
Reporter: MichaelRaskin | Owner: lele
Type: enhancement | Status: new
Priority: major | Milestone: VersionOne
Component: tailor | Version: 0.9
Keywords: heads, branching |
------------------------------+---------------------------------------------
{{{
rm -rf hg* tailor* git*
mkdir hg ; cd hg ; hg init
touch a ; hg add a ; hg ci -m a
touch b ; hg add b ; hg ci -m b
hg up -r 0
touch c ; hg add c ; hg ci -m c
cd ..
cat <<EOF >tailor.conf
[DEFAULT]
debug = True
verbose = True
[tailor]
target = git:target
start-revision = INITIAL
root-directory = /home/raskin/tmp/tailor
state-file = tailor.state
source = hg:source
subdir=tailor
[hg:source]
repository = hg
[git:target]
repository = /home/raskin/tmp/tailor/git
module = main
git-command = /var/run/current-system/sw/bin/git
EOF
tailor -D -v -c tailor.conf
}}}
This produces linear git history where "b" is first added then deleted.
With some targets (like monotone) it will even fail because of
disappearing file. Obviously, that doesn't preserve repository structure.
In the ideal world tailor would produce the same branching structure. In
slightly less ideal world I would be able specify the final revision.
Tailor could skip any revision not being ancestor of desired head or not
being descendent of previous chosen revision..
--
Ticket URL: <http://progetti.arstecnica.it/tailor/ticket/181>
Tailor <http://progetti.arstecnica.it/tailor>
An inter-VCs changeset exchanger
_______________________________________________
Tailor mailing list
[email protected]
http://lists.zooko.com/mailman/listinfo/tailor
