Version control systems
nominolo at googlemail.com
Mon Aug 11 07:18:17 EDT 2008
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
> many people would like it to be possible to override even the
> dependencies that darcs *does* find to cherry-pick patch A without
> B 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
What's missing in Git is the automatic detection of dependent
patches. Otherwise it would be straightforward to write a Darcs
frontend for Git.
Push the envelope. Watch it bend.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 194 bytes
Desc: This is a digitally signed message part
Url : http://www.haskell.org/pipermail/glasgow-haskell-users/attachments/20080811/93217baf/PGP.bin
More information about the Glasgow-haskell-users