[darcs-users] seamless git integration (Was: How to develop on a (GHC) branch with darcs)

Florent Becker florent.becker at ens-lyon.org
Thu Dec 9 13:06:31 UTC 2010


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Le 08/12/2010 13:10, Eric Kow a écrit :
> On Tue, Dec 07, 2010 at 10:46:28 -0800, Iavor Diatchki wrote:
>> PS for VCS folks: I think that an interesting idea of combining darcs
>> and git would be to use git's graph-based history model, but to
>> annotate the edges on the graph with semantic patches ala darcs.  This
>> would make it possible to write smarter auto-merge strategies for git.
> 
> Yeah, that's interesting indeed.  I got a chance to meet and chat with a
> couple of Git developers this summer, and after I explained what it was
> that makes Darcs unique, they starting wondering aloud if we could pack
> this semantic patch information into this Git concept called "notes".
> 
> You may be able think of all our work on Darcs as being laying the
> foundation for this sort of thing.  The current Darcs roadmap looks like
> this:
> 
> - short term:  performance for current users <-- we are moving away from here
> - medium term: library
> - long term:   darcs 3
> 
> But lately (talking with some people), I do wonder if we need to start
> to thinking very very hard about Seamless Git Integration, maybe so hard we
> get it done before worrying about Darcs 3.  Maybe this needs to be our
> Moon Landing:
> 
>    Darcs needs to be able to work with standard Git repositories
> 
I don't buy the "needs". But it would certainly be interesting to have
as much compatibility as possible, for instance, as a first step, being
able to push/pull between darcs and git repositories.

This comes in three degrees:
- -Ok as long as one side is private (this should be fastconvert + some UI
glue, would make most ghc hackers' dilemnas moot)
- -Ok as long as there is a centralized bridge between them: each
patch/commit crosses the border only once (a bit harder)
- -Fully distributed (there lie semantic problems and darcs/git impedance
mismatch)

Florent

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk0A1FcACgkQTCPcDztjGo7eWQCeLBWoZjYZRYOxHvFYkJrXtnX/
SZsAoIunTLby6GXLxuA6D6XVEGmbR0tu
=321r
-----END PGP SIGNATURE-----



More information about the darcs-users mailing list