<div dir="ltr"><br><br><div class="gmail_quote">2008/8/11 Thomas Schilling <span dir="ltr"><<a href="mailto:nominolo@googlemail.com">nominolo@googlemail.com</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
(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.)</blockquote>
<div><br>Darcs has a feature to deal with patches that are unrelated in patch theory but are related from the user's point of view. When you record you can use --ask-deps to specify dependent patches. These dependencies are then artificially enforced in commute (where dependencies are normally detected).<br>
<br>Note: I'm not trying to advocate anything here, I just wanted to let you know that others noticed this and added a feature for it long ago.<br><br>Jason<br></div></div></div>