On 11 Aug 2008, at 12:38, Sittampalam, Ganesh wrote:
Thomas Schilling wrote:(I am also no longer convinced that Darcs' automatic patch dependency calculations are actually a good idea. Just because two patches don't touch the same files, doesn't mean they aren't semantically dependent. Take for example "monadification" patches, which are typically submitted split up for each file. A branch captures those dependencies just fine.)But the darcs approach to dependency is what underlies cherry-picking,which many people consider the most worthwhile feature of darcs. In factmany people would like it to be possible to override even thedependencies that darcs *does* find to cherry-pick patch A without patchB that A depends on, at the expense of producing a conflict that then has to be fixed up by hand.
Cherry-picking just a single patch is simple in Git: "git cherry-pick <commit-id>"[1]. What's missing in Git is the automatic detection of dependent patches. Otherwise it would be straightforward to write a Darcs frontend for Git.
[1]: http://www.kernel.org/pub/software/scm/git/docs/git-cherry- pick.html
/ Thomas -- Push the envelope. Watch it bend.
PGP.sig
Description: This is a digitally signed message part
_______________________________________________ Glasgow-haskell-users mailing list Glasgow-haskell-users@haskell.org http://www.haskell.org/mailman/listinfo/glasgow-haskell-users
