Hello!

I'm continuing to explore Fossil and played a bit with merge's
cherrypick options...

It is quite good, although quite different than the same thing in
darcs, i.e. using fossil's 'merge --cherrypick' I was able to pick
selected 'artifact' or 'patch', but one still needs to commit it
afterwards.

Of course, in darcs one can just pull the artifact/patch into the repo
and have it since darcs can reorder patches.

otoh, I read the following in docs: " Fossil is designed in such a way
that it can be handed a set of artifacts in any order and it can
figure out the relationship between those artifacts and reconstruct
the complete development history of a software project." which invokes
feelings similar to using darc, but, obviously, Fossil is different
design.

Still, considering that Fossil is the most innovative DVCS system
after darcs, I'd appreciate if some (ex)-darcs user familiar-enough
with Fossil can shed some more light on the topic of "Fossil's best
practices in comparison with the darcs".

I saw "Coming to Fossil from darcs", but it speaks only about
rudimentary stuff...

Anyone?


Sincerely,
Gour

-- 

Gour  | Hlapicina, Croatia  | GPG key: F96FF5F6
----------------------------------------------------------------

Attachment: signature.asc
Description: PGP signature

_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Reply via email to